juju status relation data structure missing data in 3.2
This bug report was marked for expiration 311 days ago. (find out why)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Incomplete
|
High
|
Unassigned | ||
Bug Description
it used to be possible to retrieve a list of the related applications for a given endpoint from juju status --format json|yaml by looking at a related-application field. That field appears to be gone in juju 3.2.
in juju 3.1: juju status --format json | grep related-application gives a bunch of output
in juju 3.2: it doesn't.
looking at the json:
# juju 3.1:
"applications": {
"kafka": {
"relations": {
"cluster": [
{
}
]
...
# juju 3.2:
"applications": {
"kafka": {
"relations": {
"cluster": [ "cluster" ]
...
I suspect this is a regression.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Joseph Phillips (manadart) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Incomplete |
Based on diff'ing the branches there is no change in any of client command, client api, or status facade that might explain this.
Can we be sure that the actually deployment is in same across the two compared scenarios?