From ea018be298cc51c2e0fec0fcdf39a78b88b640f3 Mon Sep 17 00:00:00 2001 From: Daniele Sluijters Date: Wed, 21 Apr 2021 15:01:21 +0200 Subject: [PATCH] migration: Clarify you can migrate in-place Closes #213 --- docs/migration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/migration.md b/docs/migration.md index 02a9e832..f2b258d8 100644 --- a/docs/migration.md +++ b/docs/migration.md @@ -43,6 +43,12 @@ type: Opaque > For `host`, a URL resolvable by the cluster could look something like `postgresql..svc.cluster.local`, where `` 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 When you apply your AWX object, you must specify the name to the database secret you created above: