juju client doesn't pass version and other useful metadata to api calls

Bug #1560107 reported by Gui Bot on 2016-03-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

When the juju client makes api calls it should report the client version as part of any request. I'd also suggest we start adding the model UUID as part of those as well.

This is specifically to help support the charmstore aiding in making things seamless across versions of Juju where a feature might not be supported in the past. In particular the desire was to cheat the min-juju-version by allowing charms to add support and gating charm access in the store based on client version.

This should be passed as a header to any endpoint so that we have the ability on providing intelligent errors, or tweaking functionality to be more helpful as clients move from version to version.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta4
tags: added: juju-release-support
tags: added: 2.0-count
Changed in juju-core:
status: Triaged → Fix Released
status: Fix Released → Triaged
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers