Fix : postgres backup config reset #4507
Open
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.
Change Summary
What and Why:
Fixed PostgreSQL backup configurations being reset after
fly image update
. The issue occurred because backup settings stored in theS3_ARCHIVE_CONFIG
secret were not preserved during image updates, causing backup functionality to revert to default values and potentially disrupting backup schedules.How:
isBackupEnabled()
function to detect backup-enabled PostgreSQL apps by checking forS3_ARCHIVE_CONFIG
secretupdatePostgresOnMachines()
to check backup status before performing image updatesbackup_config_test.go
Related to:
Fixes #4340
Documentation