Skip to content
Snippets Groups Projects
Commit 3d7e3213 authored by Jörg Sachse's avatar Jörg Sachse
Browse files

fix: use ANSIBLE_VAULT_IDENTITY_LIST to enable Molecule tesing in Gitlab-CI

parent 15ae5905
No related branches found
No related tags found
No related merge requests found
......@@ -21,7 +21,7 @@ test-job:
# make sure that Ansible Vaults are present and can be decrypted
- echo "${VAULT_REPORTING}" > ../lza_reporting.pass
- echo "${VAULT_INSTALL_COMMON}" > ../lza_install_common.pass
- export ANSIBLE_VAULT_PASSWORD_FILE="../lza_reporting.pass, ../lza_install_common.pass"
- export ANSIBLE_VAULT_IDENTITY_LIST="../lza_reporting.pass, ../lza_install_common.pass"
- rm -rf ../ansible_vaults/
- git clone https://gitlab+deploy-token-25:${VAULT_ACCESS_TOKEN}@git.slub-dresden.de/slub-referat-2-3/ansible_vaults.git ../ansible_vaults/; \
# run Molecule tests
......
......@@ -2,7 +2,7 @@
# If set, configures the path to the Vault password file as an alternative to
# specifying --vault-password-file on the command line.
#vault_identity_list = ../lza_reporting.pass, ../lza_install_common.pass, ../lza_server_hardening.pass, ../slub_osquery.pass
vault_identity_list = ../lza_reporting.pass
vault_identity_list = ../lza_reporting.pass, ../lza_install_common.pass
# Path to default inventory file
# Administrators can override this by using the "-i <inventoryfile>" CLI
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment