charms should be able to expose version information about themselves (e.g. in juju status)
Bug #1762069 reported by
James Troup
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Charms should be able to expose version information about themselves to users. This would trivially allow one to know what version of the OpenStack charms one is using for example.
(I know there's a 'charm' and 'charm-rev' field already in juju status but these aren't helpful in identifying the version of the charms.)
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: charm metadata.yaml |
To post a comment you must log in.
They currently do have a way to expose payload versions (I'm running postgreqsl- 25)
"postgres 9.1.2" for xenial/
Is that sufficient, or is that confusing the "version of the charm" with
the "version of the payload". Given your comment about "Openstack Charm"
what are you looking to expose "I would support Mitaka if you wanted it,
even though you're only running Liberty".
On Sun, Apr 8, 2018 at 1:02 AM, James Troup <email address hidden>
wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1762069 /bugs.launchpad .net/juju/ +bug/1762069/ +subscriptions
>
> Charms should be able to expose version information about themselves to
> users. This would trivially allow one to know what version of the
> OpenStack charms one is using for example.
>
> (I know there's a 'charm' and 'charm-rev' field already in juju status
> but these aren't helpful in identifying the version of the charms.)
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> charms should be able to expose version information about themselves
> (e.g. in juju status)
>
> To manage notifications about this bug go to:
> https:/
>