internet/awx-operator
3
0
Fork 0
mirror of https://github.com/ansible/awx-operator.git synced 2026-05-08 06:12:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #231 from daenney/migration-docs

Browse Source 
migration: Clarify you can migrate in-place
This commit is contained in:
Shane McDonald
2021-04-21 09:15:29 -04:00
committed by GitHub
parent 51b2a211cb ea018be298
commit 6858dcfa7a
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/migration.md
View File

@@ -43,6 +43,12 @@ type: Opaque
> For `host`, a URL resolvable by the cluster could look something like `postgresql.<namespace>.svc.cluster.local`, where `<namespace>` is filled in with the namespace of the AWX deployment you are migrating data from. > For `host`, a URL resolvable by the cluster could look something like `postgresql.<namespace>.svc.cluster.local`, where `<namespace>` is filled in with the namespace of the AWX deployment you are migrating data from.
If your AWX deployment is already using an external database server or its database is otherwise not managed
by the AWX deployment, you can instead create the same secret as above but omit the `-old-` from the `name`.
In the next section pass it in through `tower_postgres_configuration_secret` instead, omitting the `_old_`
from the key and ensuring the value matches the name of the secret. This will make AWX pick up on the existing
database and apply any pending migrations. It is strongly recommended to backup your database beforehand.
## Deploy AWX ## Deploy AWX
When you apply your AWX object, you must specify the name to the database secret you created above: When you apply your AWX object, you must specify the name to the database secret you created above: