Skip to content

Conversation

vivekchavan14
Copy link

Change Summary

What and Why:
Fixed PostgreSQL backup configurations being reset after fly image update. The issue occurred because backup settings stored in the S3_ARCHIVE_CONFIG secret were not preserved during image updates, causing backup functionality to revert to default values and potentially disrupting backup schedules.

How:

  • Added isBackupEnabled() function to detect backup-enabled PostgreSQL apps by checking for S3_ARCHIVE_CONFIG secret
  • Enhanced updatePostgresOnMachines() to check backup status before performing image updates
  • Display warning message and clear remediation instructions when backups are detected
  • Added comprehensive unit tests for backup detection logic in backup_config_test.go

Related to:
Fixes #4340

Documentation

  • Fresh Produce
  • In superfly/docs, or asked for help from docs team
  • n/a

- Add support for downloading Dockerfiles from URLs (http/https)
- Fix issue where URLs were treated as local paths and concatenated with working directory
- Add URL detection and download functionality in resolveDockerfilePath
- Update dockerfile_builder to handle temporary files from downloaded URLs
- Add comprehensive unit tests for URL handling and download functionality

Fixes superfly#4464
- Add backup detection logic to check for S3_ARCHIVE_CONFIG secret before image updates
- Display warning message when backups are detected on postgres apps during image update
- Inform users to run 'fly secrets deploy' to restore backup configuration after update
- Add comprehensive unit tests for backup detection functionality

Fixes superfly#4340
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fly postgres backup config resets after image update
1 participant