-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix non-finalizing update-credential command. #8247
Conversation
Can one of the admins verify this patch? |
0581394
to
0e6b94a
Compare
0e6b94a
to
4b0a6d7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to come back and think about the interface for ClientStore().CredentialForCloud() because that seems to be the obvious place to get credentials, but it doesn't give correct credentials.
One option is to just name it GetRawCredential, or something to make it more obvious that you need to do more than just this.
4b0a6d7
to
06f1562
Compare
06f1562
to
a77bde0
Compare
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
Description of change
The
juju update-credential
command does not process credentials in the same way as other commands. The difference leaves file paths in place in user's YAML credentials file when updating credentials for JSON file based cloud credentials.QA steps
juju upgrade-juju --dry-run
- everything should work finejuju update-credential
Documentation changes
N/A
Bug reference
https://bugs.launchpad.net/juju/+bug/1738991