Cloud/credentials details should be stored in state separate from model config
Bug #1586890 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
We want to be able to refer to clouds and credentials independently of model config, e.g. so we can associate a controller with the cloud/region it was bootstrapped in; and so we can update credentials and have that propagate into the models.
We also need this so that we can have "list-controllers" show the cloud/region for controllers that are registered with "juju register". Currently that information is missing.
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| tags: | added: blocker |
| Changed in juju-core: | |
| importance: | High → Critical |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | 2.0-beta9 → 2.0-beta10 |
| Changed in juju-core: | |
| milestone: | 2.0-beta10 → 2.0-beta11 |
| Changed in juju-core: | |
| milestone: | 2.0-beta11 → 2.0-beta12 |
| Changed in juju-core: | |
| importance: | Critical → High |
| tags: | removed: blocker |
| Changed in juju-core: | |
| milestone: | 2.0-beta12 → 2.0-beta13 |
| Changed in juju-core: | |
| milestone: | 2.0-beta13 → 2.0-beta14 |
| Changed in juju-core: | |
| milestone: | 2.0-beta14 → 2.0-beta15 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 2.0-beta15 → 2.0-beta16 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta16 → none |
| milestone: | none → 2.0-beta16 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We need this in by beta9 as it fundamentally changes configuration, and we can't really upgrade. Hence blocker.