Relation IDs are not discoverable
Bug #1776665 reported by
Peter Matulis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The `remove-relation` command (and maybe others) accepts a relation ID but the latter is not discoverable by the user (an exception is with the CMR `show-offers` command). This information should be included in the output to `status --relations`.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: usability |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | removed: usability |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This is lower priority since the only part of juju which needs to use relation id is dealing with CMR offer connections, and the id is clearly shown on the relevant status output in that case. Normal non CMR relations continue to use the recommended relation key.