# AWX using local roles rather than requirements.yml, unlocking the vault **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [May 10, 2018, 7:42am UTC](https://forum.ansible.com/t/awx-using-local-roles-rather-than-requirements-yml-unlocking-the-vault/27499 "2018-05-10T07:42:10Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![anthony.cleaves](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@anthony.cleaves](https://forum.ansible.com/u/anthony.cleaves)\ **Post date:** [May 10, 2018, 7:42am UTC](https://forum.ansible.com/t/awx-using-local-roles-rather-than-requirements-yml-unlocking-the-vault/27499/1 "2018-05-10T07:42:10Z")
Hello, I was curious if anyone had any advice here. We use lots of roles we have made ourselves, they are all stored in the same project as the inventories. So I have managed to trick AWX into using them, by placing a symlin in /playbooks to …/roles `~/repos/ansible/playbooks (awx_test) └─ $ ▶ ls -al | grep roles lrwxrwxrwx 1 anthony anthony 9 May 9 12:13 roles -> ../roles/` This works fine, until we get to a role which has a file inside which is vaulted. Even though I specify the vault password, it always errors with: Identity added: /tmp/awx\_202\_5Y7d0G/credential\_3 (/tmp/awx\_202\_5Y7d0G/credential\_3) 2 Using /etc/ansible/ansible.cfg as config file 3 SUDO password: 4 Vault password: 5 ERROR! Decryption failed (no vault secrets were found that could decrypt) on /var/lib/awx/projects/\_6\_\_ansiblecode/roles/ae.apt/defaults/main.yml Is there any way to work around this? ---
**Author:** ![anthony.cleaves](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@anthony.cleaves](https://forum.ansible.com/u/anthony.cleaves)\ **Post date:** [May 10, 2018, 8:43am UTC](https://forum.ansible.com/t/awx-using-local-roles-rather-than-requirements-yml-unlocking-the-vault/27499/2 "2018-05-10T08:43:20Z")
I ssh’d to the docker container and added this to the ansible.cfg ```auto #vault_password_file = /path/to/vault_password_file ```