-
Notifications
You must be signed in to change notification settings - Fork 14
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
Improved login #33
Comments
It would be awesome if support was added for using azcli credentials like Packer , as you'd be able to use a service principle from azure pipelines and handle permissions that way. |
That should be possible now that you can mount the |
I drafted #74. Please have a look and let me know if this is on the right track to solving this issue @kichristensen , @schristoff . |
@lbergnehr Thank you for working on this, it looks like a good way to handle this issue. I have a few comments, nothing big, but I didn't want to add them to the PR yet, as it is still in draft. If you want me to add them, please let me know, just don't know how "draft" the PR is in the current state :) |
No problem adding them now from my side! I added a checklist in the PR of things I already know are missing and that I thought I'd add if I would continue finishing this up. |
Logging in is a pain right now. You have to specify it for each action, and pass in a bunch of flags and remember to suppress output:
We could add a custom login command to the mixin to simplify the default login, which assumes the default environment variable names:
In addition, we could have the mixin detect if we are logged in (a file gets stored in ~/.azure after login) before running a command and then automatically logging in if needed.
The text was updated successfully, but these errors were encountered: