Skip to content
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

[FEATURE REQUEST] Allow to cache arbitrary metadata together with a lease #48

Closed
lkubb opened this issue Apr 24, 2024 · 0 comments · Fixed by #44
Closed

[FEATURE REQUEST] Allow to cache arbitrary metadata together with a lease #48

lkubb opened this issue Apr 24, 2024 · 0 comments · Fixed by #44
Assignees

Comments

@lkubb
Copy link
Collaborator

lkubb commented Apr 24, 2024

Is your feature request related to a problem? Please describe.
Leases are typically associated with states that ensure an application has access to currently valid ones - e.g. a state/formula that manages a config file including MySQL credentials and restarts the application on changes. When a lease reaches its maximum TTL before the state is run again, the application tries to use invalid credentials.

One currently implemented solution to this is expiry events. If one has an engine module that periodically renews leases, the LeaseStore will catch that a lease can no longer be renewed and send an event, which can be reacted upon. Without having a mapping of all lease names to corresponding states, the only option is to run a highstate on the minion. If the expiry event contained information about the state that issued the lease, it would allow to selectively run only the necessary state(s).

Describe the solution you'd like
Introduce a meta field that is cached together with the lease and include it in expiry events. It should be able to contain arbitrary data.

Describe alternatives you've considered
Reacting to expiry events with a highstate.

@lkubb lkubb mentioned this issue Apr 24, 2024
3 tasks
@lkubb lkubb self-assigned this Apr 24, 2024
@lkubb lkubb closed this as completed in #44 Apr 24, 2024
@lkubb lkubb closed this as completed in 5430e54 Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant