-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Reading consul/creds/some-app results in a new consul ACL every time. #1234
Closed
Comments
Nevermind, once I get my lease configured they are garbage collected. Sorry for the noise. |
This was referenced Aug 17, 2020
3 tasks
3 tasks
3 tasks
This was referenced Feb 18, 2022
This was referenced Dec 5, 2023
5 tasks
This was referenced Feb 6, 2024
This was referenced Feb 13, 2024
Merged
This was referenced May 7, 2024
This was referenced May 20, 2024
This was referenced Jun 7, 2024
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have an issue where reading consul/creds/some-app results in a new Consul ACL every time. Is there a smart way to reread a Consul policy without creating lots and lots of copies?
Should I be setting a short ttl on the creds I generate, and counting on vault to do the clean up if the ACLs are not renewed?
I have set the lease = "1h" but the lease duration comes back as "lease_duration 2592000" (30 days?). I feel the docs are unclear on this part.
I'm using vault 0.5.2 I'll try 0.5.3 soon to see if the output is clearer.
The text was updated successfully, but these errors were encountered: