environment-tag handling permits non-unique tags
Bug #1257587 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Low
|
Unassigned |
Bug Description
Juju currently uses the environment name (user specifiable, likely to be non-unique) to identify an environment in an environment tag. We would like to change this to be a UUID.
There is currently only one user (Landscape) of environment tags, and they are going to change to using UUIDs with a temporary backwards-
We will continue to accept environment-$name as well as environment-$uuid (in fact we'll just accept environment-*); in a future release we should only accept a UUID matching the current environment's.
Changed in juju-core: | |
importance: | Medium → Low |
Changed in juju-core: | |
status: | Triaged → Fix Released |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Please mark Fix Committed when dependencies.tsv is updated in Juju, and Fix Released when it's released to the public. Closing bugs prematurely bites us when changes get left in limbo.
Also, have you confirmed that Landscape have actually changed their code to allows us to do this?