Skip to content
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

Merge "user-domain" feature branch into develop. #7099

Merged
merged 13 commits into from Mar 15, 2017

Conversation

rogpeppe
Copy link
Contributor

This adds the capability to specify a required user
domain for users, and alters the juju login command
so that it knows about public controllers.

rogpeppe and others added 13 commits January 24, 2017 12:54
This can be used to select an alternative authentication
domain when authenticating using an external identity
manager.

We also clean up the tests a little by using IsolationSuite
instead of the deprecated FakeJujuXDGDataHomeSuite,
and unexport some fields from APIContext that aren't
used.
cmd/modelcmd: support JUJU_USER_DOMAIN

This can be used to select an alternative authentication
domain when authenticating using an external identity
manager.

We also clean up the tests a little by using IsolationSuite
instead of the deprecated FakeJujuXDGDataHomeSuite,
and unexport some fields from APIContext that aren't
used.
merge origin/develop

Merge the latest origin/develop commit into this feature branch.
No conflicts worth talking about.
This is the first stage of a process that will eventually
deprecate juju register in favour of juju login.

Much of the new code in juju login is copied from
juju register.
cmd/juju/user: implement controller login

This is the first stage of a process that will eventually
deprecate juju register in favour of juju login.

Much of the new code in juju login is copied from
juju register.

To QA, try "juju login --host some-public-controller-address",
which should do the same thing as "juju register some-public-controller-address".
You could also try changing the table in getKnownControllerDomains
and doing "juju login some-alias".
merge develop branch

This merges the latest develop tip into the user-domain feature branch.
No conflicts.
cmd/juju/user: consult external directory server to find out host names for public controllers

This allows us to set up global aliases for public controllers.
cmd/juju/user: set controller name properly

Because the controller wasn't being set, the ListControllers
call was failing. The tests still passed because the ListControllers
call was entirely mocked.

Also make a backwardly incompatible change so that the old
"juju login $user" behaviour is no longer the default - to log in as
a user, the "--user" (or "-u") flag is required.
This adds the capability to specify a required user
domain for users, and alters the juju login command
so that it knows about public controllers.
Copy link

@urosj urosj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (it is a merge from feature branch)

@rogpeppe
Copy link
Contributor Author

$$merge$$

@jujubot
Copy link
Collaborator

jujubot commented Mar 15, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

@jujubot jujubot merged commit e00baf3 into juju:develop Mar 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants