Nicolas

Results 9 comments of Nicolas

@Aflynn50 I think @SimonRichardson was referring to the QA steps in https://github.com/juju/juju/pull/15940, although these won't help much because this domain is not yet fully wired up. Worth playing with that...

I completely agree with you, when adding new dimensions its very easy to get tempted with copy/pasting tests. This should improve our code quality a lot

Hi, I think I could help. I'll start with the electro ones...

This facade is used in the `containerbroker` and `provisioner` (container init) workers. I'd QA it by adding some container machines and deploying into it, something like: ``` juju add-machine lxd...

You will also need to regenerate some mocks (see the `Generate` check job): ``` go generate ./cmd/juju/commands/... go generate ./cmd/juju/user/... ```

fixed by https://github.com/juju/juju/pull/21469

Just for some context, the `storage=root:0,4:1,5:1,6:1,7:1` constraint added is juju 4 specific. Deploying postgres (16/edge) with juju 3.6 works well in the same cloud: ``` ubuntu@maastiff:~$ juju status Model Controller...