blsmith/dc-deployments-automation
1
0
Fork 0
mirror of https://bitbucket.org/atlassian/dc-deployments-automation.git synced 2025-12-14 08:53:07 -06:00
Code Issues Packages Projects Releases Wiki Activity

DCD-798: name dump as tar file and specify custom format in db_restore to workaround module not supporting custom pg_dump format

Browse Source
This commit is contained in:
Ben Partridge
2019-11-13 16:23:51 +11:00
parent e85b906019
commit 6f596c47dc
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
roles/restore_backups/tasks/main.yml
View File

@@ -76,7 +76,9 @@
overwrite: different overwrite: different
bucket: "{{ atl_backup_manifest.artifacts.sharedHome.location.location | urlsplit('hostname') }}" bucket: "{{ atl_backup_manifest.artifacts.sharedHome.location.location | urlsplit('hostname') }}"
object: "{{ atl_backup_manifest.artifacts.sharedHome.location.location | urlsplit('path') }}" object: "{{ atl_backup_manifest.artifacts.sharedHome.location.location | urlsplit('path') }}"
dest: "{{ atl_backup_home_dest }}" # We save the backup as a .tar file so that the postgresql_db module uses pg_restore instead of psql to do restore
# This can be removed when ansible 2.10 is released
dest: "{{ atl_backup_home_dest }}.tar"
- name: Install distro-specific restore support packages - name: Install distro-specific restore support packages
include_tasks: "{{ ansible_distribution|lower }}.yml" include_tasks: "{{ ansible_distribution|lower }}.yml"
@@ -96,7 +98,8 @@
template: "{{ atl_jdbc_template }}" template: "{{ atl_jdbc_template }}"
# Depends on fetch_backup roles # Depends on fetch_backup roles
state: restore state: restore
target: "{{ atl_backup_db_dest }}" target: "{{ atl_backup_db_dest }}.tar"
target_opts: "-Fc"
register: result register: result
# managed DBs in cloud providers are not allowing full root access to the DB engine, we can safely ignore the COMMENT ON EXTENSION error # managed DBs in cloud providers are not allowing full root access to the DB engine, we can safely ignore the COMMENT ON EXTENSION error
failed_when: failed_when: