master : lp:juju-backup-all : Git : Code : juju-backup-all

Get this branch:: git clone -b master https://git.launchpad.net/juju-backup-all

Members of Canonical BootStack Charmers can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:: master

Repository:: lp:juju-backup-all

Recent commits

af568b6... by Ashley James on 2023-10-23

Remove etcd_app relation check in fixture.

Merged branch ~dashmage/juju-backup-all:add-juju31-support

d3b99c9... by Ashley James on 2023-10-23

Change postgresql channel to 14/stable

ba165d0... by Ashley James on 2023-10-10

Fix unit tests

622c920... by Ashley James on 2023-09-29

func: Prevent adding relation if it already exists

Also refactor test functions.

75dc0ea... by Ashley James on 2023-09-26

Add juju 3.1 support.

* Bump python-libjuju version.
* Update logic for dealing with unit.run_action differences between juju 2 and 3.
* Change postgresql channel in func tests to edge since stable isn't working.

adfbfed... by Sudeep Bhandari on 2023-08-11

Drop Percona support

Merged branch ~sudeephb/juju-backup-all:libjuju_bump

83fa0a1... by Sudeep Bhandari on 2023-08-11

Bump libjuju to latest version - 2.9.44

71a75e5... by Ashley James on 2023-06-19

Run func-tests concurrently.

- Update series for postgreql charm to jammy since focal is not
  supported.
- Remove `model.block_until()` calls from application deployments in
  their respective fixtures. This caused one application to deploy and
  be active in its model before the next application could be deployed
  resulting in long execution times and timout errors.
- Instead, all the code creating the models and deploying the
  applications are defined in a new setup fixture called `models` which
  returns a dict containing all the models. The models, applications are
  now deployed asynchronously since the model.block_until calls are in
  separate fixtures.
- By declaring this new fixture as autouse with a session scope, the
  fixture is invoked only once automatically at the start of the test
  session, ensuring that the setup actions are performed only once.