Author: Ashley James
Author Date: 2023-10-24 07:02:57 UTC

Adopt juju 3.1

* Use juju 3.1 supported 23.10 release for juju-backup-all snap library.
* Use zaza libjuju branch in requirements.
* Remove redundant zaza dep from tox func testenv.
* func-test: Use 14/stable channel for postgresql deployment
* func-test: Use "return-code" instead of "Code"

Reviewed-on: https://code.launchpad.net/~dashmage/charm-juju-backup-all/+git/charm-juju-backup-all/+merge/453229
Reviewed-by: Eric Chen <eric.chen@canonical.com>
Reviewed-by: 🤖 prod-jenkaas-bootstack <webops+prod-jenkaas-bootstack@canonical.com>
Reviewed-by: JamesLin <james.lin@canonical.com>
Reviewed-by: Chi Wai CHAN <chiwai.chan@canonical.com>

Author: Facundo Ciccioli
Author Date: 2022-08-30 11:14:40 UTC

Adjust tests for the omitting models' feature

In the way, fix the cronjob command, which was passing a CSV as the only
--omit-models parameter, but that was not having the intended effect on
the auto_backup.py script.

Author: Facundo Ciccioli
Author Date: 2022-08-29 11:20:27 UTC

Disable DEBUG logging

Author: Facundo Ciccioli
Author Date: 2022-08-25 13:20:02 UTC

Bump juju-backup-all to that repo's current master

Author: Facundo Ciccioli
Author Date: 2022-05-10 14:21:34 UTC

Move juju-backup-all tool ref to point to current latest