Releases: sil-org/postgresql-backup-restore
Releases · sil-org/postgresql-backup-restore
5.1.7 - quieter, cleaner logs
What's Changed
Full Changelog: 5.1.6...5.1.7
5.1.6 - fix fatal bug
Fixed
- Fixed fatal bug introduced in 5.1.5 that aborts backup (or restore) because sha256sum in busybox (in alpine image) does not support
--checkand--silentswitches.
Full Changelog: 5.1.5...5.1.6
5.1.5 - log consistency
What's Changed
Full Changelog: 5.1.4...5.1.5
5.1.4 - fix AWS key variables
Deprecated
- Deprecated the old-style AWS key variables:
AWS_ACCESS_KEYandAWS_SECRET_KEY.
Fixed
- Added backward compatibility for the old-style variables to form a bridge to the AWS-compatible variables
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY.
What's Changed
Full Changelog: 5.1.3...5.1.4
5.1.3 - fix S3_BUCKET bug introduced in 5.1.2
What's Changed
Full Changelog: 5.1.2...5.1.3
5.1.2 - **BROKEN**
What's Changed
- Rename docker-compose.yml to compose.yaml by @briskt in #24
- use the AWS CLI instead of s3cmd by @briskt in #25
Full Changelog: 5.1.1...5.1.2
Filter sensitive values from Sentry events
What's Changed
- Filter sensitive values from Sentry events by @Praveenraj-K in #23
Full Changelog: 5.1.0...5.1.1
Release 5.1.0 - Updated the restore script to verify checksum file
What's Changed
- Updated the Backup Restore Script by @Praveenraj-K in #22
- Downloads database backup and checksum files from an S3 bucket
- Decompresses the backup and checksum files
- Validates backup integrity using SHA-256 checksum verification
- Restores the database from the backup file
- Implements error handling with Sentry integration for error reporting
- Cleans up temporary files after successful restoration
Full Changelog: 5.0.3...5.0.4