Hashicorp Vault lookup Plugin #11674
Merged
Conversation
This file contains 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
| from ansible.errors import * | ||
| from ansible.plugins.lookup import LookupBase | ||
|
|
||
| try: |
There was a problem hiding this comment.
this should be moved into the run method, as we only want this to error on running, not on loading, which will always happen if this is included in ansible.
or in the hasivault class init, which gets called from run.
bcoca
added
the
needs_revision
|
@bcoca done |
ansibot
added
feature
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a lookup plugin to be able to read secrets from a Hashicorp Vault endpoint.
Requires
pip install hvacUsage is like
lookup('hashi_vault', 'secret=secret/hello token=c975b780-d1be-8016-866b-01d0f9b688a5 url=http://myvault:8200')Where url is optional and defaults to localhost and can also read in from the VAULT_ADDR environment variable.
This first iteration doesn't support other authentication mechanisms other than token and also presumes the vault is unsealed prior to executing the lookup.