Breaking API change landing for 2.0-beta10
Tim Penhey
tim.penhey at canonical.com
Tue Jun 21 04:55:28 UTC 2016
Hi folks,
This impacts all people calling the Juju API directly. If you use the
juju client, you *should* be fine.
Taking advantage of our time in "beta", we are adding consistency to the
wire-protocol used by the juju client to talk to the juju apiserver.
In general this means that all the parameters are lower-case with words
separated with dashes. *Error returns should all be "omitempty" meaning
that if there was no error, there is no "error" entry in the return.
There is no API facade version bump with this change. This allows us to
start 2.0 with a clean and consistent slate.
The change can be found here:
https://github.com/juju/juju/pull/5674
This change will be landing very soon, perhaps by the time you read this
message.
Cheers,
Tim
More information about the Juju-dev
mailing list