Add Database Backup Feature (Disabled by Default) and Use postgres User for Multi-DB Support #6
+181
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New features:
The backup feature is disabled by default. To enable it, set
database_backup_enabled: trueand provide a value fordatabase_backup_output_path.You can set the backup path, schedule, how many old backups to keep, file ownership, and more—all through variables.
Previously, backups used the
opencastdatabase user. Now, the role uses thepostgresuser by default for backups. This makes it much easier to back up multiple databases (likeopencast,tobira, etc.) with a single setup, sincepostgrescan access all databases by default. No need to create extra users or adjust configs for each DB.Just list the databases you want to back up in the
database_backup_dbsvariable, for example: