Optionally read VAULT_PASSWORD from .vaulctl file#75
Open
Conversation
Contributor
|
This feature goes against the purpose of the secretsmanager and the vaultctl client, which is to avoid storing real passwords on the filesystem and to use short-lived tokens instead, in order to reduce the risk of password leaks. |
Contributor
Author
|
I need a reliable solution that allows me to mass deploy Jenkins instances without an interactive password prompt. Only relying on a cached access token has proven unreliable. Please provide an alternative solution. |
Contributor
|
It is reliable: tokens expire only after 8 hours. This was verified yesterday during a test. Controls in Jiro should be improved by using vaultctl status. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.