Releases: metal-stack/backup-restore-sidecar
Releases · metal-stack/backup-restore-sidecar
v0.11.1
General Changes
- Use individual lifecycle policies per object prefix to allow sidecars to act on a single bucket (#111) @simcod
- Fix typo in container name (#107) @simcod
- Migrate to aws-sdk-go-v2 (#81) @robertvolkmann
- Update go deps and proto creation (#99) @majst01
Actions Required
A bug has been fixed in the backup-restore-sidecar that occurred when the backup-restore-sidecar was configured to store multiple backups in the same bucket with different object prefixes. The sidecar now creates individual lifecycle rules for the object prefixes such that they do not overwrite each others configurations.
If you use such a configuration, it is required to clean up the old lifecycle rule that does not match an object prefix after rolling out this version of the backup-restore-sidecar.
🚀 Features
v0.11.0
v0.10.3
General Changes
- Update all dependencies (#94) @majst01
- Don't create multiple backupers, which can interfere. (#96) @Gerrit91
- Ensure a restore from a fresh disk always takes the latest backup (#92) @majst01
- Factor out duplicate code in the backup-providers (#90) @majst01
- Migrate to buf v2 and update database versions (#89) @majst01
- Update dependencies all over the place (#88) @majst01
- Update modules and fix typos (#86) @majst01
- fix(meili): wait more patiently (#85) @vknabel