juju does not have an update-credential command
Bug #1713582 reported by
Richard Harding
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
In Progress
|
High
|
Anastasia | ||
2.2 |
Fix Released
|
High
|
Anastasia |
Bug Description
As Juju expands users go through credentials, or they have credentials they used to bring up a model and want to shift to org based creds. There's no mechanism in Juju for a user to update the credentials of a production deployed model. Users need the ability to perform something of an update-credential and choose either new info (interactive) or the name of another credential that the client is aware of.
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Anastasia (anastasia-macmood) |
milestone: | none → 2.3-alpha1 |
Changed in juju: | |
milestone: | 2.3-beta1 → 2.3-beta2 |
Changed in juju: | |
milestone: | 2.3-beta2 → none |
To post a comment you must log in.
Notes to this:
Juju should validate it can successfully use a credential before swapping them over. We've had issues in some controllers where users have pulled creds of running models and now are unable to remove the model.
This also seems like a situation where a user should be able to remove a model that the credentials don't work for. It might just throw warnings at the list of instances that are going to be abandoned if there's running infrastructure that Juju cannot clear out due to a bad credential.