-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Support ephemeral keys #238
Labels
type/enhancement
Proposed improvement or new feature
Comments
This will be highly useful. I am currently evaluating consul and I would need to workaround this lacking feature. The idea is to have one node regularly iterating keys and if the lock has one away, delete them. |
Fixed by #487 |
duckhan
pushed a commit
to duckhan/consul
that referenced
this issue
Oct 24, 2021
* server-acl-init: Add -server-address and -server-port * [Breaking change] Require -server-address to be provided instead of discovering the server IPs from Kubernetes pods. This allows us to eventually to run this command against external servers or servers deployed on Kube in the same way. On Kubernetes, instead of discovering Pod IPs, we can use server's stateful set DNS names. * [Breaking change] Remove -expected-replicas, -release-name, and -server-label-selector flags because we no longer need them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to modify Sessions to take a "behavior" configuration. By default the behavior will be "release", which means any associated locks of the session will be freed. However, a new "delete" behavior will be added which enables associated keys to be deleted. In effect, these KV pairs become ephemeral since they are cleared when the session is invalidated.
The text was updated successfully, but these errors were encountered: