Releases: juju/juju-restore
Release list
v0.17
Contributors
Assets 3
v0.16
What's Changed
- fix: add missing ssl arg to controller restore by @wallyworld in #28
Full Changelog: v0.15...v0.16
Contributors
Assets 3
v0.15
What's Changed
- feat: add support for using mongo 4.4.30 by @wallyworld in #27
Full Changelog: v0.14...v0.15
Contributors
Assets 3
juju-restore v0.14
Add support for cloning secret backend rotations to the --copy-controller option.
See #25 .
juju-restore v0.13
Add support for cloning secret backends to the --copy-controller option.
See #24 .
juju-restore v0.12
Add a new --copy-controller option to initialise a new controller to look like a backed up controller.
This is useful when setting up a controller for a newer Juju version and copying to that new controller users, clouds, and config from an existing controller.
See #23.
juju-restore v0.11
Use normal (non-raw) standard input for prompts; add --yes option. See #19.
juju-restore v0.10
Fixes problems when controller is running Focal (due to paths being different when mongorestore is installed via a Snap). See #18
juju-restore v0.9
This release extends juju-restore to support downgrading a controller by restoring a backup taken before the controller was upgraded. This is prevented by default, but can be enabled by passing the --allow-downgrade option.
v0.9 also adds auto-loading credentials from the current machine's agent.conf file, and fixes a bug (#12) in the code that miscounted how many HA nodes are in a backup.
juju-restore v0.5
This initial release of juju-restore supports restoring a Juju backup into the same controller it was taken from. It will only allow restoring when the Juju version and HA configuration are the same as when the backup was created. Future versions will relax these restrictions to allow using restore to rollback failed upgrades, and restore into a new controller for disaster recovery purposes.