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

ANSIBLE_VAULT_PASSWORD related instructions do not seem to work as documented with EE's. #1728

Open
netopsengineer opened this issue Apr 1, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@netopsengineer
Copy link

ISSUE TYPE
  • Doc issue
SUMMARY

The document section in question: link

image

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 switch run to exec and printenv, 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.

@netopsengineer netopsengineer added documentation Improvements or additions to documentation new New issues and PRs to triaged labels Apr 1, 2024
@audgirka audgirka removed the new New issues and PRs to triaged label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Roadmap
Development

No branches or pull requests

3 participants