chore: preserve md5 auth scheme if project used it before the upgrade

Author: pcnc

ansible/files/admin_api_scripts/pg_upgrade_scripts/complete.sh

@@ -11,7 +11,7 @@ SCRIPT_DIR=$(dirname -- "$0";)
 # shellcheck disable=SC1091
 source "$SCRIPT_DIR/common.sh"
 
-LOG_FILE="/tmp/pg-upgrade-complete.log"
+LOG_FILE="/var/log/pg-upgrade-complete.log"
 
 function cleanup {
     UPGRADE_STATUS=${1:-"failed"}
@@ -45,6 +45,9 @@ function complete_pg_upgrade {
     echo "4. Running generated SQL files"
     retry 3 run_generated_sql
 
+    echo "4.1. Applying correct authentication scheme"
+    retry 3 use_corect_auth_scheme
+
     sleep 5
 
     echo "5. Restarting postgresql"
@@ -70,6 +73,15 @@ function run_generated_sql {
     fi
 }
 
+# Projects which had their passwords hashed using md5 need be 
+# configured to use md5 on upgraded instances as well, as opposed to scram-sha-256
+function use_corect_auth_scheme {
+    PASSWORD_ENCRYPTION_SETTING=$(run_sql -A -t -c "SHOW password_encryption;")
+    if [ "$PASSWORD_ENCRYPTION_SETTING" = "md5" ]; then
+        sed -i 's/scram-sha-256/md5/g' /etc/postgresql/pg_hba.conf
+    fi
+}
+
 function start_vacuum_analyze {
     echo "complete" > /tmp/pg-upgrade-status
     su -c 'vacuumdb --all --analyze-in-stages' -s "$SHELL" postgres

ansible/files/admin_api_scripts/pg_upgrade_scripts/initiate.sh

@@ -282,6 +282,9 @@ EOF
     mkdir -p "$MOUNT_POINT/conf"
     cp -R /etc/postgresql-custom/* "$MOUNT_POINT/conf/"
 
+    # removing wal-g config as to allow it to be explicitly enabled on the new instance
+    rm -f "$MOUNT_POINT/conf/wal-g.conf"
+
     # copy sql files generated by pg_upgrade
     echo "11. Copying sql files generated by pg_upgrade"
     mkdir -p "$MOUNT_POINT/sql"