-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 new AzureCLI authentication options for GenerateResourcesAndImage and Packer templates #10602
base: main
Are you sure you want to change the base?
Conversation
Fixed slight adjustment to suggestion in #10236 to properly handle the error if not logged in, it would not enter the |
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.
Tested UseAzureCliAuth option based on the code above and works as expected.
@mikhailkoliada @shamil-mubarakshin |
We are currently waiting for this as well, since we prefer to use OIDC authentication (federated) instead of client secrets in our devops pipelines. Would be great if this can be released short term. Thanks! |
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.
i got that azufe certific in an milestone oslt. check where its from =) its been an few days bender.
Description
This PR introduces new authentication options for the GenerateResourcesAndImage.ps1 helper script and the Packer templates for
ubuntu
andwindows
. By leveraging theuse_azure_cli_auth
optional value in Packerazure-arm
builder (ref) this PR provides new ways to authenticate while building the runner-images.UseAzureCliAuth
is introduced in the helper script.az login
.AzureClientId
parameterfalse
in both the helper-script and packer-templates and does not break the approach of using SPN authenticationWhat advantages does using the new switch give?
Application Developer
orApplication Administrator
to run script / build withoutAzureClientId
andAzureClientSecret
inputs.AzureClientId
andAzureClientSecret
inputs.Azure Pipeline example using new UseAzureCliAuth switch
Service-connection is using Azure managed identity and federated credentials
Azure Pipeline example using old SPN method
Service-connection is using Azure managed identity and federated credentials
Running locally using my az login credentials only
Related issue:
#10236 - I added the suggestion to let active
az login
be used if foundCheck list