juju units should have globally unique identifier for hooks/charms
Bug #1814828 reported by
Richard Harding
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
High
|
Unassigned | ||
Bug Description
in a CMR world it's helpful, without identifying the units themselves to have data that is specific to a unit, the big example is secrets with vault. The secrets are generated per unit but since the units aren't identified across a CMR you can't have this process work out. Having a global (across any controller, model, application) unit id would be the best path forward and allow the relation there to leverage that to track which secret should be given to which unit.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | 2.6-beta1 → 2.6-beta2 |
| Changed in juju: | |
| milestone: | 2.6-beta2 → 2.6-rc1 |
| Changed in juju: | |
| milestone: | 2.6-rc1 → 2.6-rc2 |
| Changed in juju: | |
| milestone: | 2.6-rc2 → 2.6.1 |
| Changed in juju: | |
| milestone: | 2.6.1 → 2.6.2 |
| Changed in juju: | |
| milestone: | 2.6.2 → 2.6.3 |
| Changed in juju: | |
| milestone: | 2.6.3 → 2.6.4 |
| Changed in juju: | |
| milestone: | 2.6.4 → 2.6.5 |
| Changed in juju: | |
| milestone: | 2.6.5 → 2.6.6 |
| Changed in juju: | |
| milestone: | 2.6.6 → 2.6.7 |
| Changed in juju: | |
| status: | Triaged → Invalid |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju: | |
| milestone: | 2.6.7 → 2.6.8 |
To post a comment you must log in.
The remote unit names for a CMR are unique - the local model sees any connecting application named as remote-<uuid> and hence any remote units will be remote-<uuid>/0, remote-<uuid>/1 etc. So essentially the unit names are unique across controller, model etc. Does that help?