Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
cmd/modelcmd: inject jujuclient.ClientStore #4419
Conversation
axw
added some commits
Feb 14, 2016
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$FUUUUUUUUUUUUUUU$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
added a commit
that referenced
this pull request
Feb 15, 2016
jujubot
merged commit 04ea27f
into
juju:cloud-credentials
Feb 15, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
axw commentedFeb 15, 2016
And some related changes to prepare for using jujuclient everywhere:
and a model name. Model names are relative
to controller names, and a client can know
about two models with the same name for
different controllers
which will refresh the client's knowledge
of models in the specified controller for
the current user
refresh the client's model cache if an
unknown model is specified. This means you
can do "juju status -m " for a model
that you haven't previously switched to.
and use it to get the current model for the
current controller. We still honour the
current-model file, until all of the tests
stop relying on it
model names in either format "model", or
"controller:model". In the first format,
the current controller is assumed. This
method now records the controller name for
use when opening API connections.
(Review request: http://reviews.vapour.ws/r/3859/)