juju get output is not compatible with juju set or juju deploy

[Aaron Bentley]

Juju provides a way to retrieve settings as yaml; juju get. It provides several ways to set settings from yaml: "juju deploy --config", and "juju set --config". But these yaml formats are incompatible, so you can't use "juju get" to retrieve a service's settings, then use "juju (deploy|set) --config" to apply these settings to another deployment. This is surprising.

[Domas Monkus (tasdomas)]

I guess the default output format of `juju get` should not be changed. Should we consider adding a command line parameter (e.g. --reuse)?

[Aaron Bentley (abentley)]

A command-line option on "get" would work, but I think it would be more convenient for users if "set" were changed to transparently accept get-style yaml.

If there is a command-line option, --format=set seems like a good one. Or --set-style if --format=set is not usable for some reason.

[Domas Monkus (tasdomas)]

Submitted pull request: https://github.com/juju/juju/pull/1788

[Domas Monkus (tasdomas)]

I've submitted a pull request to fix this, but it still needs reviews: http://reviews.vapour.ws/r/1116/

[Aaron Bentley (abentley)]

Incomplete means cannot be verified.