charm channels only visible in show-application

[Andrea Ieri]

It looks like the only way to determine if a charm has been deployed from a given channel is to run juju show-application for every deployed application. The charm channel is shown neither in an exported bundle, nor in a yaml-format status.

This makes it hard to validate a model with tools like juju-lint.

[John A Meinel (jameinel)]

It feels like something that could be in 'juju status --format=yaml'.

On Thu, Jan 28, 2021 at 1:20 PM Andrea Ieri <email address hidden>
wrote:

> Public bug reported:
>
> It looks like the only way to determine if a charm has been deployed
> from a given channel is to run juju show-application for every deployed
> application. The charm channel is shown neither in an exported bundle,
> nor in a yaml-format status.
>
> This makes it hard to validate a model with tools like juju-lint.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1913631
>
> Title:
> charm channels only visible in show-application
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1913631/+subscriptions
>

[James Troup (elmo)]

John A Meinel <email address hidden> writes:

> It feels like something that could be in 'juju status --format=yaml'.

Surely it should be in the bundle as well? Otherwise you can't use
bundles to a) duplicate environments or b) determine differences (at
the model level) between two environments by diffing bundles?

--
James

[Simon Richardson (simonrichardson)]

In progress PR: https://github.com/juju/juju/pull/12638

[Simon Richardson (simonrichardson)]

Additionally, the changes for export-bundle need to be reflected in diff-bundle. This is handled in the following PR: https://github.com/juju/juju/pull/12641