-
Notifications
You must be signed in to change notification settings - Fork 105
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
ANSIBLE_VAULT_PASSWORD related instructions do not seem to work as documented with EE's. #1728
Comments
@rseabra it looks like you introduced this documentation on #1714 could you comment on how it is to be used? From everything I can gather, there is no support for Any help would be appreciated. |
~~There is a typo that nobody noticed. It's ANSIBLE_VAULT_PASSWORD_FILE! ~~ I'm off work and without access to my setup in order to checkout if there's an actual typo, because I'm almost 100% sure that the point was to load the password into a variable, and not a file that's not actually available in the container. I'll let you know next week. |
@rseabra appreciate the reply, yeah I figured that might be the case, but even then I was not sure how it would work, as You essentially need a file with the output of If you were able to work around this, or this is some |
"&%$#"%$#&"# I documented it wrong, I will fix the faq but here's the proper trick:
|
I added #1799 in order to resolve. |
Thanks a lot for finding out my error in the documentation patch, it's a neat trick and it deserves to be properly documented. :) |
ISSUE TYPE
SUMMARY
The document section in question: link
I am able to to create the gpg encrypted file, and the shell script, and it does work independently when executed, I do in fact get the password back. However, when executing with the EE as documented, the ENV is inside the EE container, but Ansible seems to simply ignore it:
ANSIBLE_VAULT_PASSWORD="$( ~/bin/vault.sh )" ansible-navigator run (...)
Is the behavior that is expected such that
ANSIBLE_VAULT_PASSWORD=my_plain_text_password
would be inside the EE? If so, I do see that if I switchrun
toexec
andprintenv
, but the playbook does not seem to use it, first task executed with something vaulted says there were not credentials available.A vault password or secret must be specified to decrypt
The previous instructions that revolve around linking the password file or script into the project that are considered the less secure options per the docs, do work for me as documented. I just prefer the newly mentioned method above. FWIW, I am on MacOS 14.4.1, and
ansible-navigator 24.2.0
.The text was updated successfully, but these errors were encountered: