AWX using local roles rather than requirements.yml, unlocking the vault

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?

I ssh’d to the docker container and added this to the ansible.cfg

#vault_password_file = /path/to/vault_password_file