Currently, the Ansible workflow doesn't work as documented. I identified the following contributing issues:
1) the account listed on the Ansible node was Cyberark instead of cyberark, this is apparently case sensitive
2) the ansible/nodes layer to which the Ansible host belongs wasn't granted permissions on anything in the entitlements for the secrets/frontend/db_password variable
3) the secrets.yml file asks for a secret called /secrets/frontend/db_password which chokes, but it likes secrets/frontend/db_password just fine
4) you can't just run ./pullpassword.sh or even summon ./pullpassword.sh, you gotta run summon sh ./pullpassword.sh
These issues are resolved in this pull request and the Ansible workflow as documented in the walkthrough will complete without a hitch.
Currently, the Ansible workflow doesn't work as documented. I identified the following contributing issues: 1) the account listed on the Ansible node was
Cyberarkinstead ofcyberark, this is apparently case sensitive 2) theansible/nodeslayer to which the Ansible host belongs wasn't granted permissions on anything in the entitlements for thesecrets/frontend/db_passwordvariable 3) thesecrets.ymlfile asks for a secret called/secrets/frontend/db_passwordwhich chokes, but it likessecrets/frontend/db_passwordjust fine 4) you can't just run./pullpassword.shor evensummon ./pullpassword.sh, you gotta runsummon sh ./pullpassword.shThese issues are resolved in this pull request and the Ansible workflow as documented in the walkthrough will complete without a hitch.