finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Make use of matrix_postgres_db_migration_request.caller

Browse Source
This commit is contained in:
Slavi Pantaleev 2020-12-14 16:13:57 +02:00
parent ac37091d01
commit c1431b28f0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
roles/matrix-postgres/tasks/util/migrate_db_to_postgres.yml
View File

@ -34,7 +34,7 @@
- name: Fail if we cannot migrate on the current architecture ({{ matrix_architecture }})
fail:
msg: >-
{{ matrix_postgres_db_migration_request.engine_variable_name }} has been set to `postgres` (which is our new default now).
{{ matrix_postgres_db_migration_request.engine_variable_name }} (part of {{ matrix_postgres_db_migration_request.caller }}) has been set to `postgres` (which is our new default now).
However, we've discovered an existing file-based database ({{ matrix_postgres_db_migration_request.engine_old }}) in {{ matrix_postgres_db_migration_request.src }}.
It appears that you've been using this bridge with a file-based database engine until now.
To continue using {{ matrix_postgres_db_migration_request.engine_old }}, opt into it explicitly: add `{{ matrix_postgres_db_migration_request.engine_variable_name }}: {{ matrix_postgres_db_migration_request.engine_old }}` to your vars.yml file and re-run this same command.