Accept new / unknown API fields gracefully (#131)
authorCory Johns <johnsca@gmail.com>
Thu, 1 Jun 2017 18:14:54 +0000 (14:14 -0400)
committerGitHub <noreply@github.com>
Thu, 1 Jun 2017 18:14:54 +0000 (14:14 -0400)
commit676078b6d332065bb1efc59638b0568f929259b0
treee247ff581f0a463d620bc8886f798c4ae872936a
parent13947f8cad6aa0c5d6063718da597bafec100008
Accept new / unknown API fields gracefully (#131)

* Accept new / unknown API fields gracefully

From discussions in Montreal, it seems that new fields in the Juju
schema definitions are expected to be handled gracefully even without a
bump to the facade version. That is, facade versions will only be bumped
if a field is removed or changed.

Fixes #130

* Update schema and generated code for juju-2.2-rc1

The agent-version field that was added to ModelInfo is of a type that
requires some special parsing and serialization logic.  This type was
used before but not in an API that we were apparently exercising.
13 files changed:
CONTRIBUTORS
docs/index.rst
docs/upstream-updates/index.rst [new file with mode: 0644]
juju/client/_client1.py
juju/client/_client2.py
juju/client/_client3.py
juju/client/_client5.py
juju/client/_definitions.py
juju/client/facade.py
juju/client/overrides.py
juju/client/schemas-juju-2.2-rc1.json [new file with mode: 0644]
juju/client/schemas-juju-latest.json [changed from file to symlink]
tests/unit/test_overrides.py [new file with mode: 0644]