Wade Barnes
The backup scripts are currently being refactored to support a plugin model (and mongo support). Adding this sort of functionality may be easier once that is complete.
> I'm interested in this as well, using Postgis extension of Postgres 13, and just starting to look at using backup container. Once the upgrade is complete, the Postgis extension...
@MScallion, Other then the `createuser: error: creation of new role failed: ERROR: role "postgres" already exists`, it looks like it's running. So you're issue may be due to the way...
> Should the Environment Name be the namespace? Yes, but that shouldn't effect the verification.
@MScallion, You are missing environment variables for `PATRONI_MASTER_DEV_USER` and `PATRONI_MASTER_DEV_PASSWORD`, as defined here; https://github.com/BCDevOps/backup-container#backupconf
Examples: DC - https://github.com/bcgov/orgbook-configurations/blob/master/openshift/templates/backup/backup-deploy.yaml#L128-L147 backup.conf - https://github.com/bcgov/orgbook-configurations/blob/master/openshift/templates/backup/config/backup.conf#L39-L40
That would be causing these lookups to return blank strings and cause the startup to fail; https://github.com/BCDevOps/backup-container/blob/master/docker/backup.postgres.plugin#L119-L120
> When I updated the app database to v13 I did not contribute the changes because I split the database user into a DB owner and an application proxy user....
Those values are a customization that need to be done for each application of the container when you use the `backup.conf` file to define the backups and schedule. I was...
> So for our application database we have used the following parameters in the deployment template; > > ``` > - name: DATABASE_USER > valueFrom: > secretKeyRef: > name: ${DATABASE_DEPLOYMENT_NAME}...