juju does not have an update-credential command

Bug #1713582 reported by Richard Harding
This bug report is a duplicate of:  Bug #1735402: juju azure auth stopped working. Edit Remove
6
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.

Revision history for this message
Richard Harding (rharding) wrote :

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.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

This is kind of related to bug # 1611076. That bug talks about renaming a credential but I wonder if both renaming and update could be done as one fix...

Revision history for this message
Anastasia (anastasia-macmood) wrote :

Triaging as High as there are couple of interesting and intriguing scenarios where this is extremely useful.

Changed in juju:
status: New → Triaged
importance: Undecided → High
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Anastasia (anastasia-macmood)
milestone: none → 2.3-alpha1
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Richard Harding,

Please clarify :D

There is an API method on "Cloud" facade - UpdateCredentials [1].

Do you need a command for it?

[1]
on 2.2: https://github.com/juju/juju/blob/2.2/apiserver/cloud/cloud.go#L183
on develop: https://github.com/juju/juju/blob/develop/apiserver/facades/client/cloud/cloud.go#L237

Revision history for this message
Anastasia (anastasia-macmood) wrote :

So, it looks like the command and the facade to update existing cloud credentials exist.

I have added a clarification in 'update-credential' command on 2.2: https://github.com/juju/juju/pull/7812

For further releases of Juju, we might look at clarifying commands names and behavior to disambiguate user experience.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

Helpdoc forward-port on develop (heading into 2.3): https://github.com/juju/juju/pull/7816

Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Changed in juju:
milestone: 2.3-beta2 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am marking this bug as a duplicate since 'update-credential' command exist. It currently works on at a controller-scope meaning that you need to know what credential your model uses before you call this command.

I am tracking improvements to this command in bug # 1735402 (see comment# 18, Part 4)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.