relation not complete for juju status formats other then tabular
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
juju status tabular format provides the following information for relationships
Relation provider,
However, formats for yaml and json do not provide a one to one mapping for relations.
Ie. There is no non-ambiguous linkage between a relation provider and requirer
Additionally there is no information provided about the interface at all.
For example given the following relation provided by:
juju status --relations
Relation provider Requirer Interface Type
ceph-mon:client cinder-ceph:ceph ceph-client regular
Output from juju status --format yaml is missing a one to one mapping of the relations
ceph-mon:
charm: cs:ceph-mon-58
...
application
current: active
message: Unit is ready and clustered
since: 07 Oct 2021 22:58:41Z
relations:
client:
- cinder-ceph <--- No way to map this to cinder-ceph:ceph without making assumptions
- glance
- gnocchi
- landscape-client
- nova-compute
- prometheus-
juju-info:
- filebeat
- logrotated
- rsyslog-
- telegraf
mon:
- ceph-mon
nrpe-
- nrpe
osd:
- ceph-osd
radosgw:
- ceph-radosgw
----
cinder-ceph:
charm: cs:cinder-ceph-264
...
application
current: active
message: Unit is ready
since: 07 Oct 2021 23:03:51Z
relations:
ceph:
- ceph-mon <--- No way to map this non-ambiguously
ceph-access:
- nova-compute
storage-
- cinder
subordinate-to:
- cinder
Also interface is not in the yaml and json formats at all in this case ceph-client.
This one to one mapping is required for juju lint bug https:/ /bugs.launchpad .net/juju- lint/+bug/ 1840814