Releases: significa/fly-pg-dump-to-s3
Releases · significa/fly-pg-dump-to-s3
v3.2.0
v3.1.0
v3.0.1
v3.0.0
What's Changed
Breaking changes:
From version 3 fly-pg-dump-to-s3 uses Fly machines API (also known as Fly apps v2). You must migrate, or re-create your db backup worker fly apps:
- Remove the FLY_API_TOKEN environment variable:
fly secrets unset FLY_API_TOKEN -a YOUR_APP
- Migrate your app to v2:
fly migrate-to-v2 -a YOUR_APP
- Start making use of
trigger-backup.sh
or the action.github/workflows/trigger-backup.yaml
to trigger the backup.
More information in the readme.
Full Changelog: v2.0.0...v3.0.0
v2.0.0
What's Changed
- Fix: typos by @tofran in #3
Breaking change:<prefix>S3_DESTINATON
env var is now<prefix>S3_DESTINATION
. - pg_dump args update, conditionally tar only for directory backups and documentation by @tofran in #4
Breaking change: Default pg_dump args changed. - CI/CD improvements by @tofran in #5
- fix: github workflows permissions by @tofran in #6
Full Changelog: v1.1.0...v2.0.0
v1.1.0
What's Changed
- feat: utils to create aws and fly resources by @guilherme1805 in #1
- Scaling with volumes instead of instance count and improvements by @tofran in #2
Upgrading
- To update the image run
fly deploy --image ghcr.io/significa/fly-pg-dump-to-s3:1.1.0
- If you are scaling to zero, change your trigger to
fly volumes create --no-encryption --size $SIZE_IN_GB --region $REGION temp_data
and scale the app to 1fly scale count 1
.
Refer to the readme for more details.
New Contributors
- @guilherme1805 made their first contribution in #1
- @tofran made their first contribution in #2
Full Changelog: v1.0.0...v1.1.0