juju deploy --dry-run does not catch option errors in bundle

[Nicolas Pochet]

When deploying (or applying a new config to an existing model) a bundle some might want to ensure that everything is correct.
To do so, we can use the --dry-run flag.
When doing so, juju does not validate the options as it does it without the --dry-run flag.
For example, if we take this simple bundle:

applications:
  ubuntu:
    charm: cs:ubuntu
    options:
      foo: bar

The ubuntu charm does not have the foo option. If we try to validate the bundle with juju deploy --dry-run, we get the following output:

juju deploy bundle.yaml --dry-run
Resolving charm: cs:ubuntu
Executing changes:
- upload charm cs:ubuntu-12
- deploy application ubuntu using cs:ubuntu-12

Everything seems to be fine according to juju.
If we want to deploy, without dry-run, then we get the error that we expect:

juju deploy bundle.yaml
Resolving charm: cs:ubuntu
Executing changes:
- upload charm cs:ubuntu-12
- deploy application ubuntu using cs:ubuntu-12
ERROR cannot deploy bundle: cannot deploy application "ubuntu": unknown option "foo"

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.