automatically prefix control bucket with the environment name
Bug #901311 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
helps prevent any copy paste errors from the env from turning into operational issues. users typically get this value autogenerated for them, and dont have context for its significance. we should highlight in the docs the immutability of env names.
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in juju: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in juju: | |
| status: | Confirmed → Triaged |
| Changed in juju: | |
| importance: | Medium → Low |
To post a comment you must log in.
Confirming, as I've seen at least 2 people accidentally confuse the env by bootstrapping twice with the same control bucket. May need to be done delicately as this could potentially break backward compatibility.