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] Add vault_lease beacon module #53

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

[FEATURE REQUEST] Add vault_lease beacon module #53

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

Comments

@lkubb
Copy link
Member

lkubb commented Apr 24, 2024

Is your feature request related to a problem? Please describe.
Secret backends other than the KV one usually issue leases that expire with time. If one wants to leverage Salt to manage these leases, there should be a process that:

  1. periodically renews the leases (this is achieved by just requesting them from the store regularly)
  2. warns when they cannot be extended anymore or have expired

Describe the solution you'd like
Add a beacon module that monitors a lease and warns when it runs out.

Describe alternatives you've considered
This could also be achieved with an engine module, especially 1.. 2. is the definition of the use case for a beacon module. Since there is also functionality in Salt to create a beacon when running a state (mod_beacon), it would make sense to use a beacon for 2..

The already implemented expiry events only work when a Salt invocation requests the lease.

@lkubb lkubb self-assigned this Apr 24, 2024
@lkubb lkubb mentioned this issue May 14, 2024
3 tasks
@lkubb lkubb closed this as completed in #50 Jul 22, 2024
@lkubb lkubb closed this as completed in 9c327dd Jul 22, 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