Missing overview over charm bindings
Bug #1672997 reported by
Sandor Zeestraten
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
With the networking changes in 2.1.x and containers, there needs to be a way to list which bindings a charm has available and which are used/bound to a space when deployed.
Either under "juju status <unit> --format yaml" or perhaps something like "juju list-bindings <unit>"
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: 4010 |
| tags: | added: canonical-bootstack |
Revision history for this message
| Alvaro Uria (aluria) wrote | #1 |
Revision history for this message
| Richard Harding (rharding) wrote | #2 |
| Changed in juju: | |
| milestone: | none → 2.6-beta1 |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I checked a Juju 2.3.2 environment and "juju status --format yaml ceilometer" didn't show the bindings it has. "juju status --format yaml", either.
In a Juju 2.3.3 environment, there are no commands for bindings (show/list/...).