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.

Sign up for GitHub

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

Jump to bottom

Force new revision when latest secrets are used in environment #4

Open
garbetjie opened this issue Jun 28, 2021 · 0 comments
Open

Force new revision when latest secrets are used in environment #4

garbetjie opened this issue Jun 28, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@garbetjie
Copy link
Owner

At the moment, when the latest version of secrets are exposed through the environment, this value is not updated to reflect the latest version. This will only happen on a cold start, and never if instances are kept warm. This is not an issue when mounting secrets as volumes.

There should be the functionality provided to force a new revision to be (optionally) created if any secrets using the latest version are exposed through environment variables.
@garbetjie garbetjie added the enhancement New feature or request label Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@garbetjie