-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kv.put() method with Consul v1.10.1 results in KV entries that are visible via CLI/API, but not UI #231
Comments
I've since created a branch in the aforementioned repo that feeds the Jenkins pipeline that does this to use the |
Hey y'all, any updates here? |
if you look at your UI: https://user-images.githubusercontent.com/629551/208970185-64790602-675b-4641-8cdf-827ab87b3f5c.png you'll see a login button... if this is in the API, this is done -> either you are not using the Consul UI correctly (not using the login button to see keys or the UI not having the right token to see keys), either it is a bug in Consul UI Alternatively, try using consul kv get to see results or try pushing first an alternative (simpler k/v)... look at a basic hello world key.... does this works? (look at doc on hashi learn on how using K/V with simple examples) Regards |
Using the Diplomat gem as part of an internal Jenkins pipeline to take a .json file as a source of truth and insert the whole JSON payload into the KV. Our use-case here is using a GitOps workflow to ensure
mcrouter
configurations laid down byconsul-template
are only managed by this GitOps workflow (Jenkins Pipeline).It successfully inserts into the intended Consul KV, but is only visible via the CLI/API and not via the UI. I am unsure if this is a Diplomat gem problem or if this is something wrong or incorrectly configured with our Consul clusters. The test I'd conducted below was done against a Development cluster only and in a test KV path to avoid trampling configurations in production. Any thoughts or ideas as to why this is happening?
Script invoked by the Jenkins pipeline:
Results:
The text was updated successfully, but these errors were encountered: