Pass whether service is primary or subordinate via relation
Bug #1568161 reported by
Haw Loeung
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Hi,
Is it possible to include whether a service/charm is primary or subordinate via the relation (which currently passes unit name, public, and private IP, and service name).
An example of where this is useful would be in the NRPE monitoring charms where it generates hostnames using servicename and unit number. Unfortunately, this can fail because it could be using the wrong relation to work out service name and unit number.
tags: | added: charm subordinate |
tags: | added: canonical-is |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.1.0 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Seems like it wouldn't be too difficult to add this information. I'll ask for some input on how to best convey the info.