-
Notifications
You must be signed in to change notification settings - Fork 502
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
Fixes lp#1848104: updating existing credential with invalid value invalidates other credentials #10801
Fixes lp#1848104: updating existing credential with invalid value invalidates other credentials #10801
Conversation
…eeds to be model specific based on the facade call arguments.
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.
A couple of questions about how state is gotten
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.
Looks good to go.
Main comment is to use st directly instead of m.State()
(we used st to get Model() in the first place)
Or m.UUID() in one place.
|
fatal: The remote end hung up unexpectedly |
unrelated failure in github.com/juju/juju/worker/raft/raftflag.TestPackage |
|
Description of change
On the controller facades, creating cloud call context in the facade construction makes no sense since call context is model specific.
This PR changes the creation of the context to be in the actual facade call methods. All context creation has been moved to the calls that use context rather than forcing it to happen too early and for every call.
QA steps
steps in bug report do not result in the controller model cloud credential to be invalidated.
Bug reference
https://bugs.launchpad.net/juju/+bug/1848104