-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add option to azure login action with service principals and az acr login
intwostep-container-build
#14
Conversation
…service principals
az acr login
and the azure login action with service principalsaz acr login
and azure login action with service principals to twostep-container-build
az acr login
and azure login action with service principals to twostep-container-build
az acr login
intwostep-container-build
Awesome, thanks for the contribution, @dylanhmorris! We should probably add a test using |
Added a test, but this repo will now need the self-hosted runners set up. We can use the STF service principal for now, but in the long run we should probably have a service principal for CFA actions itself. |
Alright, I just made a small tweak to reflect the new version of the action (1.2.1 vs 1.2.0). We can deal with adding a self-hosted runner later. I will approve, merge, and release so you can start using this ASAP in pyrenew. Thanks again! |
This should be a more robust approach. It should be more secure and should also help with CDCgov/pyrenew-hew#321
Also makes the docker login action inputs optional, since they are only needed and used if you go that route. I also see some argument that the action shouldn't attempt to log in at all, and the user should handle that upstream in their workflow.