Juju API lacks version endpoint

Bug #1609910 reported by Tim Van Steenburgh on 2016-08-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Wishlist
Unassigned

Bug Description

A websocket client connected to a Juju API server should be able to determine which version of Juju it is connected to before making API calls (to login, for example).

Richard Harding (rharding) wrote :

To add on to this, I've found it it very valuable in the past to actually embed info such as the git sha of the project into that version data so that you can easily identify what build is actually running. This is really useful for development purposes. I rebuilt juju and wanted to make sure that the build worked and my version was correct but --version just notes that it's betaXX and I couldn't find a way to get a real sha to verify it was using what I thought it was.

I also enjoy projects that have a health/ endpoint that reveals what the system considers the health of the environment to be. It could perhaps list a lot of different data, including git sha and version.

tags: added: feature
Changed in juju-core:
status: New → Triaged
importance: Undecided → Wishlist
affects: juju-core → juju
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers