jjx's juju deploy command does not parse --config key=value, so integration tests that pass config at deploy time (via jubilant's deploy(config=...)) silently drop the config overrides. juju deploy should accept --config and apply the overrides on top of the charmcraft defaults, matching real Juju's behavior.
jjx's
juju deploycommand does not parse--config key=value, so integration tests that pass config at deploy time (via jubilant'sdeploy(config=...)) silently drop the config overrides.juju deployshould accept--configand apply the overrides on top of the charmcraft defaults, matching real Juju's behavior.