5.1.4 - fix AWS key variables

Deprecated

• Deprecated the old-style AWS key variables: AWS_ACCESS_KEY and AWS_SECRET_KEY.

Fixed

• Added backward compatibility for the old-style variables to form a bridge to the AWS-compatible variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.

What's Changed

• change the AWS access key variables to the AWS CLI standard by @briskt in #27

Full Changelog: 5.1.3...5.1.4

5.1.3 - fix S3_BUCKET bug introduced in 5.1.2

What's Changed

• remove s3:// S3_BUCKET prefix added in error by @briskt in #26

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

Release 5.0.3 - Fix for Checksum

What's Changed

• Fix for Checksum by @Praveenraj-K in #21

Full Changelog: 5.0.2...5.0.3

Added Checksum -5.0.2

What's Changed

• Added Checksum by @Praveenraj-K in #20

Full Changelog: 5.0.1...5.0.2

Fix for Python 3.12.4 constrain

What's Changed

• Fix for Python 3.12.3 constrained by @Praveenraj-K in #18

Full Changelog: 5.0.0...5.0.1

Added -Sentry Notification

What's Changed

• Changed in the Branch setting and tags by @Praveenraj-K in #14
• Delete .whitesource by @briskt in #15
• Feature data img by @Praveenraj-K in #16
• Fix for Sentry by @Praveenraj-K in #17

New Contributors

• @Praveenraj-K made their first contribution in #14
• @briskt made their first contribution in #15

Full Changelog: 4.0.1...5.0.0

Use current DB owner during restore

Changes

• Constrain Python version to 3.12.3. s3cmd version 2.4.0 with Python 3.12.4 on Alpine 3.20 fails with an AttributeError.
• Find and use the current database owner when dropping the database during a restore operation. PostgreSQL requires the user executing a DROP DATABASE statement to be the database owner. PostgreSQL databases are initially owned by the user postgres before the ownership is set to the DB user. Restoring data to a brand new database requires a different user than restoring to an existing database.