-
Notifications
You must be signed in to change notification settings - Fork 491
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 add-credential help documentation. #8161
Conversation
Can one of the admins verify this patch? |
!!build!! |
We should never require the user specify "/dev/stdin". If we want to do something like that, we should support using "-" to mean stdin. |
Is this PR good for approval? |
I would defer to Andrew who did the actual changes to how we initialize
Azure. I know at one point we had a rather difficult set of steps because
Azure wanted us to create groups, etc. It seems we probably automated most
of that inside Juju, but I wouldn't be able to tell if the new config was
correct without direct tests and I'm away from my machines right now.
It looks reasonable, but I can't confirm it's correctnes here.
John
=:->
…On Dec 1, 2017 14:08, "Eric" ***@***.***> wrote:
Is this PR good for approval?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8161 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAMYfRp6-jCFBWvqxBI47rxq1IIo5YYTks5s79AFgaJpZM4QxOdT>
.
|
OK, will defer @axw |
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.
LGTM, thanks
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
Description of change
The
juju add-credentail
help documentation is incorrect.QA steps
Feeding the help message's example credential file to an
add-credential
command that use it should work:Then edit
example_creds.yaml
with valid azure credentialsThen you should be able to bootstrap a controller on azure. Notice how before this patch bootstrapping using this method would fail since
tenant_id
is not recognized by juju's credential validation and adding it to the file would result in the following error when bootstrapping:Documentation changes
The online documentation is also incorrect. A PR is has been opened with the relevant fix.
Bug reference
https://bugs.launchpad.net/juju/+bug/1690920