Skip to content

#1882 - Recovery and backup startegy patroni #2057

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Jun 30, 2023
Merged

#1882 - Recovery and backup startegy patroni #2057

Show file tree
Hide file tree
Changes from 13 commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
7a82c9e
updated
guru-aot Jun 27, 2023
633ab60
updated
guru-aot Jun 27, 2023
cf507e8
updated
guru-aot Jun 28, 2023
776fbd6
updated
guru-aot Jun 28, 2023
ef1537b
updated
guru-aot Jun 28, 2023
9d8e91d
updated
guru-aot Jun 28, 2023
1849c1e
updated
guru-aot Jun 28, 2023
b854b56
updated
guru-aot Jun 28, 2023
653f2ec
updated
guru-aot Jun 28, 2023
3c180d7
updated
guru-aot Jun 28, 2023
79b9f71
updated
guru-aot Jun 28, 2023
93fdd3c
updated
guru-aot Jun 28, 2023
a1644e8
updated
guru-aot Jun 29, 2023
be48c0c
Updated
guru-aot Jun 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
162 changes: 54 additions & 108 deletions devops/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,10 @@ export HOST_PREFIX := $(or $(HOST_PREFIX), $$HOST_PREFIX)
export NEW_DB := $(or $(NEW_DB), $$NEW_DB)
export JOB_NAME := $(or $(JOB_NAME), $$JN)
export SITE_MINDER_LOGOUT_URL := $(or $(SITE_MINDER_LOGOUT_URL), https://logontest7.gov.bc.ca/clp-cgi/logoff.cgi)
export BACKUP_POSTGRESQL_APP_NAME := $(or $(BACKUP_POSTGRESQL_APP_NAME), postgresql-backup)
export BACKUP_MONGODB_APP_NAME := $(or $(BACKUP_MONGODB_APP_NAME), mongodb-backup)
export BACKUP_CONFIGMAP_NAME := $(or $(BACKUP_CONFIGMAP_NAME), backup-conf)
export PATRONI_SIMSDB_BACKUP_APP_NAME := $(or $(PATRONI_SIMSDB_BACKUP_APP_NAME), patroni-simsdb-backup)
export PATRONI_SIMSDB_BACKUP_CONFIGMAP_NAME := $(or $(PATRONI_SIMSDB_BACKUP_CONFIGMAP_NAME), patroni-simsdb-backup-conf)
Copy link
Collaborator

@andrewsignori-aot andrewsignori-aot Jun 28, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When this was mentioned "The backup.conf should be created for databases separately" does it means that they need to be created per database or per database type? For instance, Mongo/Postgres? In case we have a second DB on Postgres, do we need to create a second backup structure?
IMO, the answer to this question can help determine the variable's names.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah for seperate database not the database type, because individual databases can have different schedule of backups

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, "The backup.conf should be created for databases separately" actually means that the backups can be configured for multiple databases but we are actually structuring it in a way that it will be per database assuming that a new database will have a different backup schedule, right?

Does it mean that in the future, if we have more than one DB, instead of a new line in a config file we will create a separate structure to handle the new backup?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes you got it right, that was the plan, as individual backup stratergy for different databases.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went through the conversation @guru-aot @andrewsignori-aot .

@guru-aot what could be the benefit of having individual backup strategy per db?

export PATRONI_SIMSDB_BACKUP_CONFIG_FILE_NAME := $(or $(PATRONI_SIMSDB_BACKUP_CONFIG_FILE_NAME), patroni-simsdb-backup.conf)
export PATRONI_SIMSDB_BACKUP_VERIFICATION_VOLUME_MOUNT_PATH := $(or $(PATRONI_SIMSDB_BACKUP_VERIFICATION_VOLUME_MOUNT_PATH), /var/lib/postgresql/data)
export BYPASS_CRA_INCOME_VERIFICATION := $(or $(BYPASS_CRA_INCOME_VERIFICATION), false)
export BYPASS_APPLICATION_SUBMIT_VALIDATIONS := $(or $(BYPASS_APPLICATION_SUBMIT_VALIDATIONS), false)
export SWAGGER_ENABLED := $(or ${SWAGGER_ENABLED}, true)
Expand Down Expand Up @@ -143,16 +144,15 @@ oc-build-forms: | print-status build-forms
oc-deploy-ha-mongo: | print-status deploy-ha-mongo
oc-deploy-forms: | print-status deploy-forms

# Create/delete backup structure
# Create/delete config map shared accross postgresql and mongodb.
oc-db-backup-configmap-init: | print-status db-backup-configmap
oc-db-backup-configmap-delete: | print-status db-backup-configmap-delete
# Create/delete structure for postgresql.
oc-db-backup-init-postgresql: | print-status db-backup-build-postgresql db-backup-deploy-postgresql
oc-db-backup-delete-postgresql: | print-status db-backup-build-delete-postgresql db-backup-deploy-delete-postgresql
# Create/delete structure for mongodb.
oc-db-backup-init-mongodb: | print-status db-backup-build-mongodb db-backup-deploy-mongodb
oc-db-backup-delete-mongodb: | print-status db-backup-build-delete-mongodb db-backup-deploy-delete-mongodb
# Build backup structure.
oc-db-backup-patroni-simsdb-build: | print-status db-backup-build-patroni
oc-db-backup-patroni-simsdb-build-delete: | print-status db-backup-build-patroni-delete

# Create/delete backup structure.
# Create/delete structure for patroni.
oc-db-backup-patroni-simsdb-deploy: | print-status db-backup-configmap db-backup-deploy-patroni
oc-db-backup-patroni-simsdb-deploy-delete: | print-status db-backup-configmap-delete db-backup-deploy-patroni-delete


print-status:
@echo " +---------------------------------------------------------+ "
Expand Down Expand Up @@ -490,127 +490,73 @@ deploy-forms:
$(call rollout_and_wait,dc/$(FORMS_NAME))

# Create database backup structure (build/configmap/deploy)

# Create the config map to be shared by POSTGRES and mongodb.
db-backup-configmap:
test -n "$(NAMESPACE)"
test -n "$(BACKUP_POSTGRESQL_APP_NAME)"
test -n "$(BACKUP_MONGODB_APP_NAME)"
@echo "+\n++ Creating configmap resources for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) create configmap $(BACKUP_CONFIGMAP_NAME) --from-file=./openshift/database-backup/backup.conf

db-backup-configmap-delete:
test -n "$(NAMESPACE)"
@echo "+\n++ Removing configmap resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) delete configmap/$(BACKUP_CONFIGMAP_NAME)

# Create the POSTGRES structure
db-backup-build-postgresql:
db-backup-build-patroni:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this also include SIMS to be aligned with the other renamed variables?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i specifically did not add SIMS, becuase build is going to be same for all, but while deploying we can have multiple databases with different names.

test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_POSTGRESQL_APP_NAME)"
test -n "$(PATRONI_SIMSDB_BACKUP_APP_NAME)"
@echo "+\n++ Creating build resources for database backups on $(BUILD_NAMESPACE)\n+"
oc -n $(BUILD_NAMESPACE) process -f ./openshift/database-backup/backup-build.yaml \
-p NAME=$(BACKUP_POSTGRESQL_APP_NAME) OUTPUT_IMAGE_TAG=v1 \
-p BASE_IMAGE_FOR_BUILD=artifacts.developer.gov.bc.ca/docker-remote/centos/postgresql-12-centos7:20200917-804ef01 \
-p NAME=$(PATRONI_SIMSDB_BACKUP_APP_NAME) OUTPUT_IMAGE_TAG=v1 \
-p BASE_IMAGE_FOR_BUILD=quay.io/fedora/postgresql-14:14 \
| oc -n $(BUILD_NAMESPACE) apply -f -

db-backup-build-delete-postgresql:
db-backup-build-patroni-delete:
test -n "$(NAMESPACE)"
test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_POSTGRESQL_APP_NAME)"
test -n "$(PATRONI_SIMSDB_BACKUP_APP_NAME)"
@echo "+\n++ Removing build resoures for database backups on $(NAMESPACE)\n+"
oc -n $(BUILD_NAMESPACE) delete is/$(BACKUP_POSTGRESQL_APP_NAME) bc/$(BACKUP_POSTGRESQL_APP_NAME)
oc -n $(BUILD_NAMESPACE) delete is/$(PATRONI_SIMSDB_BACKUP_APP_NAME) bc/$(PATRONI_SIMSDB_BACKUP_APP_NAME)

db-backup-deploy-postgresql:
test -n "$(NAMESPACE)"
test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_POSTGRESQL_APP_NAME)"
@echo "+\n++ Creating deploy config resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) process -f ./openshift/database-backup/backup-deploy.yaml \
-p NAME=$(BACKUP_POSTGRESQL_APP_NAME) \
-p IMAGE_NAMESPACE=$(BUILD_NAMESPACE) \
-p SOURCE_IMAGE_NAME=$(BACKUP_POSTGRESQL_APP_NAME) \
-p TAG_NAME=v1 \
-p FTP_SECRET_KEY=$(BACKUP_POSTGRESQL_APP_NAME)-ftp-secret \
-p BACKUP_VOLUME_NAME=$(BACKUP_POSTGRESQL_APP_NAME)-pvc \
-p BACKUP_VOLUME_SIZE=20Gi \
-p VERIFICATION_VOLUME_SIZE=5Gi \
-p ENVIRONMENT_NAME=$(NAMESPACE) \
-p CONFIG_MAP_NAME=$(BACKUP_CONFIGMAP_NAME) \
-p VERIFICATION_VOLUME_NAME=$(BACKUP_POSTGRESQL_APP_NAME)-verification-pvc \
-p DATABASE_SERVER_NAME=PATRONI_MASTER \
-p DATABASE_SECRET_NAME=patroni-creds \
-p DATABASE_SECRET_USER_KEY_NAME=superuser-username \
-p DATABASE_SECRET_PASSWORD_KEY_NAME=superuser-password \
-p ENVIRONMENT_FRIENDLY_NAME='SIMS $(NAMESPACE) POSTGRESQL DB Backups' \
| oc -n $(NAMESPACE) apply -f -

db-backup-deploy-delete-postgresql:
# Create the config map to be shared by POSTGRES.
db-backup-configmap:
test -n "$(NAMESPACE)"
test -n "$(BACKUP_POSTGRESQL_APP_NAME)"
@echo "+\n++ Removing deploy resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) delete \
secret/$(BACKUP_POSTGRESQL_APP_NAME) \
secret/$(BACKUP_POSTGRESQL_APP_NAME)-ftp-secret \
dc/$(BACKUP_POSTGRESQL_APP_NAME) \
networkpolicy/$(BACKUP_POSTGRESQL_APP_NAME)
# The below PVCs are not deleted.
# pvc/$(BACKUP_POSTGRESQL_APP_NAME)-pvc \
# pvc/$(BACKUP_POSTGRESQL_APP_NAME)-verification-pvc \

# Create the MONGODB structure
db-backup-build-mongodb:
test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_MONGODB_APP_NAME)"
@echo "+\n++ Creating build resources for database backups on $(BUILD_NAMESPACE)\n+"
oc -n $(BUILD_NAMESPACE) process -f ./openshift/database-backup/backup-build.yaml \
-p NAME=$(BACKUP_MONGODB_APP_NAME) OUTPUT_IMAGE_TAG=v1 \
-p BASE_IMAGE_FOR_BUILD=artifacts.developer.gov.bc.ca/redhat-docker-remote/rhscl/mongodb-36-rhel7 \
| oc -n $(BUILD_NAMESPACE) apply -f -
test -n "$(PATRONI_SIMSDB_BACKUP_APP_NAME)"
@echo "+\n++ Creating configmap resources for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) create configmap $(PATRONI_SIMSDB_BACKUP_CONFIGMAP_NAME) --from-file=./openshift/database-backup/$(PATRONI_SIMSDB_BACKUP_CONFIG_FILE_NAME)

db-backup-build-delete-mongodb:
db-backup-configmap-delete:
test -n "$(NAMESPACE)"
test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_MONGODB_APP_NAME)"
@echo "+\n++ Removing build resoures for database backups on $(NAMESPACE)\n+"
oc -n $(BUILD_NAMESPACE) delete is/$(BACKUP_MONGODB_APP_NAME) bc/$(BACKUP_MONGODB_APP_NAME)
@echo "+\n++ Removing configmap resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) delete configmap/$(PATRONI_SIMSDB_BACKUP_CONFIGMAP_NAME)

db-backup-deploy-mongodb:
# Deploy POSTGRES backup container.
db-backup-deploy-patroni:
test -n "$(NAMESPACE)"
test -n "$(BUILD_NAMESPACE)"
test -n "$(BACKUP_MONGODB_APP_NAME)"
test -n "$(PATRONI_SIMSDB_BACKUP_APP_NAME)"
@echo "+\n++ Creating deploy config resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) process -f ./openshift/database-backup/backup-deploy.yaml \
-p NAME=$(BACKUP_MONGODB_APP_NAME) \
-p NAME=$(PATRONI_SIMSDB_BACKUP_APP_NAME) \
-p IMAGE_NAMESPACE=$(BUILD_NAMESPACE) \
-p SOURCE_IMAGE_NAME=$(BACKUP_MONGODB_APP_NAME) \
-p SOURCE_IMAGE_NAME=$(PATRONI_SIMSDB_BACKUP_APP_NAME) \
-p TAG_NAME=v1 \
-p FTP_SECRET_KEY=$(BACKUP_MONGODB_APP_NAME)-ftp-secret \
-p BACKUP_VOLUME_NAME=$(BACKUP_MONGODB_APP_NAME)-pvc \
-p BACKUP_VOLUME_SIZE=5Gi \
-p VERIFICATION_VOLUME_SIZE=1Gi \
-p FTP_SECRET_KEY=$(PATRONI_SIMSDB_BACKUP_APP_NAME)-ftp-secret \
-p BACKUP_VOLUME_NAME=$(PATRONI_SIMSDB_BACKUP_APP_NAME)-pvc \
-p BACKUP_VOLUME_SIZE=20Gi \
-p VERIFICATION_VOLUME_SIZE=5Gi \
-p ENVIRONMENT_NAME=$(NAMESPACE) \
-p CONFIG_MAP_NAME=$(BACKUP_CONFIGMAP_NAME) \
-p VERIFICATION_VOLUME_NAME=$(BACKUP_MONGODB_APP_NAME)-verification-pvc \
-p DATABASE_SERVER_NAME=MONGO \
-p DATABASE_SECRET_NAME=mongodb-creds \
-p DATABASE_SECRET_USER_KEY_NAME=username \
-p DATABASE_SECRET_PASSWORD_KEY_NAME=password \
-p ENVIRONMENT_FRIENDLY_NAME='SIMS $(NAMESPACE) MONGO DB Backups' \
| oc -n $(NAMESPACE) apply -f -
-p CONFIG_MAP_NAME=$(PATRONI_SIMSDB_BACKUP_CONFIGMAP_NAME) \
-p CUSTOM_CONFIG_FILE_NAME=$(PATRONI_SIMSDB_BACKUP_CONFIG_FILE_NAME) \
-p VERIFICATION_VOLUME_NAME=$(PATRONI_SIMSDB_BACKUP_APP_NAME)-verification-pvc \
-p VERIFICATION_VOLUME_MOUNT_PATH=$(PATRONI_SIMSDB_BACKUP_VERIFICATION_VOLUME_MOUNT_PATH) \
-p DATABASE_DEPLOYMENT_NAME=patroni-creds \
-p DATABASE_USER_KEY_NAME=superuser-username \
-p DATABASE_PASSWORD_KEY_NAME=superuser-password \
-p ENVIRONMENT_FRIENDLY_NAME='SIMS $(NAMESPACE) POSTGRESQL DB Backups' \
| oc -n $(NAMESPACE) apply -f -

db-backup-deploy-delete-mongodb:
db-backup-deploy-patroni-delete:
test -n "$(NAMESPACE)"
test -n "$(BACKUP_MONGODB_APP_NAME)"
test -n "$(PATRONI_SIMSDB_BACKUP_APP_NAME)"
@echo "+\n++ Removing deploy resoures for database backups on $(NAMESPACE)\n+"
oc -n $(NAMESPACE) delete \
secret/$(BACKUP_MONGODB_APP_NAME) \
secret/$(BACKUP_MONGODB_APP_NAME)-ftp-secret \
dc/$(BACKUP_MONGODB_APP_NAME) \
networkpolicy/$(BACKUP_MONGODB_APP_NAME)
secret/$(PATRONI_SIMSDB_BACKUP_APP_NAME) \
secret/$(PATRONI_SIMSDB_BACKUP_APP_NAME)-ftp-secret \
dc/$(PATRONI_SIMSDB_BACKUP_APP_NAME) \
networkpolicy/$(PATRONI_SIMSDB_BACKUP_APP_NAME)
# The below PVCs are not deleted.
# pvc/$(BACKUP_MONGODB_APP_NAME)-pvc
# pvc/$(BACKUP_MONGODB_APP_NAME)-verification-pvc
# pvc/$(PATRONI_SIMSDB_BACKUP_APP_NAME)-pvc \
# pvc/$(PATRONI_SIMSDB_BACKUP_APP_NAME)-verification-pvc \

# Remove redis and resources including secrets from openshift namespace.
delete-redis:
Expand Down
4 changes: 1 addition & 3 deletions devops/openshift/database-backup/backup-build.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,6 @@ objects:
strategy:
type: Docker
dockerStrategy:
pullSecret:
name: artifactory-secret-credential
from:
kind: DockerImage
name: ${BASE_IMAGE_FOR_BUILD}
Expand Down Expand Up @@ -73,4 +71,4 @@ parameters:
displayName: FROM Image Tag
description: Base image to build from. Docker creds or Artificatory setup may be needed to alleviate docker rate-limiting
required: true
value: artifacts.developer.gov.bc.ca/docker-remote/centos/postgresql-12-centos7:20200917-804ef01
value: docker.io/centos/postgresql-12-centos7:20200917-804ef01
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

artifacts.developer.gov.bc.ca/docker-remote is not the same as docker.io?
Are we not supposed to be using the artifacts URL as much as possible (if not for everything)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you are right, but in this case, the build.yaml has been copied from the https://github.com/BCDevOps/backup-container/blob/master/openshift/templates/backup/backup-build.yaml. And the base image is actually not uses this too instead it uses quay.io/fedora/postgresql-14:14, as per the suggestion from the bcgov developer who did the changes to the dockerfile, which supports postgres 14.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@guru-aot does artifacts.developer.gov.bc.ca/docker-remote/centos/postgresql-12-centos7:20200917-804ef01 work? as artifacts.developer.gov.bc.ca/docker-remote is just a proxy.
Correct me if wrong.

IMO only if it does not work we should start thinking about docker.io IMO.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we claim that current backup supports postgres 14 with this image?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it supports Postgres 14, as per the fedora postgres 14 base image

38 changes: 16 additions & 22 deletions devops/openshift/database-backup/backup-deploy.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,6 @@ objects:
app: ${APP_NAME}
role: ${ROLE}
env: ${TAG_NAME}
app.kubernetes.io/part-of: ${GROUP_LABEL}
spec:
strategy:
type: Recreate
Expand Down Expand Up @@ -141,7 +140,7 @@ objects:
configMap:
name: ${CONFIG_MAP_NAME}
items:
- key: ${CONFIG_FILE_NAME}
- key: ${CUSTOM_CONFIG_FILE_NAME}
path: ${CONFIG_FILE_NAME}
containers:
- name: ${NAME}
Expand Down Expand Up @@ -170,16 +169,16 @@ objects:
value: ${MONGODB_AUTHENTICATION_DATABASE}
- name: TABLE_SCHEMA
value: ${TABLE_SCHEMA}
- name: ${DATABASE_SERVER_NAME}_USER
- name: DATABASE_USER
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we removing the "_USER" because we will no longer support the backup for multiple DBs?
"_USER" reference: https://github.com/BCDevOps/backup-container/tree/master#backupconf

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we decide to move away from back-up of multiple db in same backup container?

If there is a requirement in future to have a another db, or we if decide to back up redis(by any chance) current way will be easily adaptable right?

valueFrom:
secretKeyRef:
name: ${DATABASE_SECRET_NAME}
key: ${DATABASE_SECRET_USER_KEY_NAME}
- name: ${DATABASE_SERVER_NAME}_PASSWORD
name: ${DATABASE_DEPLOYMENT_NAME}
key: ${DATABASE_USER_KEY_NAME}
- name: DATABASE_PASSWORD
valueFrom:
secretKeyRef:
name: ${DATABASE_SECRET_NAME}
key: ${DATABASE_SECRET_PASSWORD_KEY_NAME}
name: ${DATABASE_DEPLOYMENT_NAME}
key: ${DATABASE_PASSWORD_KEY_NAME}
- name: FTP_URL
valueFrom:
secretKeyRef:
Expand Down Expand Up @@ -271,22 +270,17 @@ parameters:
description: This is only required if you are backing up mongo database with a separate authentication database.
required: false
value: ""
- name: DATABASE_SECRET_NAME
- name: DATABASE_DEPLOYMENT_NAME
displayName: Database Deployment Name
description: The name associated to the database deployment resources. In particular, this is used to wire up the credentials associated to the database.
required: true
value: postgresql
- name: DATABASE_SERVER_NAME
displayName: Database server name
description: Database server name all uppercase. Should be the same server name from backup.conf file (e.g. PATRONI_MASTER).
required: true
value: SERVER_NAME
- name: DATABASE_SECRET_USER_KEY_NAME
- name: DATABASE_USER_KEY_NAME
displayName: Database User Key Name
description: The database user key name stored in database deployment resources specified by DATABASE_DEPLOYMENT_NAME.
required: true
value: database-user
- name: DATABASE_SECRET_PASSWORD_KEY_NAME
- name: DATABASE_PASSWORD_KEY_NAME
displayName: Database Password Key Name
description: The database password key name stored in database deployment resources specified by DATABASE_DEPLOYMENT_NAME.
required: true
Expand Down Expand Up @@ -380,6 +374,11 @@ parameters:
description: Used for backward compatibility only. Ignored when using the recommended `backup.conf` and cron backup strategy. Period (d,m,s) between backups in a format used by the sleep command
required: false
value: ""
- name: CUSTOM_CONFIG_FILE_NAME
displayName: Custom Config File Name
description: The name of the custom configuration file.
required: true
value: backup.conf
- name: CONFIG_FILE_NAME
displayName: Config File Name
description: The name of the configuration file.
Expand Down Expand Up @@ -449,9 +448,4 @@ parameters:
displayName: Resources Memory Limit
description: The resources Memory limit (in Mi, Gi, etc) for this build.
required: true
value: 0Mi
- name: GROUP_LABEL
displayName: Group label
description: Group label for backup structure.
required: true
value: backups
value: 0Mi
3 changes: 0 additions & 3 deletions devops/openshift/database-backup/backup.conf → ...atabase-backup/patroni-simsdb-backup.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,4 @@
postgres=patroni-master:5432/SIMSDB
postgres=patroni-master:5432/FFA_API_DB
postgres=patroni-master:5432/FFA_BPM_DB
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

mongo=mongo:27017/formio

# Run a backup at 1am Pacific every day.
0 1 * * * default ./backup.sh -s
Expand Down