DEV-1058 bugfix backup process

- hard coded gpg key
qa
Sven Ketelsen 3 years ago
parent 2d8755cf34
commit dab25a4090

@ -1,2 +1,3 @@
---
backup_communication_keys_repository: "https://{{ gitea_admin_username | urlencode() }}:{{ gitea_admin_password | urlencode() }}@{{ shared_service_hostname_gitea }}/gitea-admin/communication-keys.git"
backup_communication_keys_stage_gpg_key: "smardigo_automation_{{ stage }}.gpg.pub"

@ -0,0 +1,3 @@
---
# TODO use stage specific gpg key
backup_communication_keys_stage_gpg_key: "smardigo_automation_prodnso.gpg.pub"

@ -36,7 +36,7 @@
# there is no ansible gpg module already in place
# linting violation needs to be whitelisted
- name: "Importing stage specific automation gpg-key" # noqa command-instead-of-shell
shell: 'gpg --import {{ tempdir.path }}/smardigo_automation_{{ stage }}.gpg.pub'
shell: 'gpg --import {{ tempdir.path }}/{{ backup_communication_keys_stage_gpg_key }}'
# there is no ansible module already in place for (mariabackup|gpg)
# so using shell module

@ -33,7 +33,7 @@
# there is no ansible gpg module already in place
# linting violation needs to be whitelisted
- name: "Importing stage specific automation gpg-key" # noqa command-instead-of-shell
shell: 'gpg --import {{ tempdir.path }}/smardigo_automation_{{ stage }}.gpg.pub'
shell: 'gpg --import {{ tempdir.path }}/{{ backup_communication_keys_stage_gpg_key }}'
# there is no ansible module already in place for (pg_basebackup|gpg)
# so using shell module

Loading…
Cancel
Save