-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: ARM template deployment az login fails when using certificate for authentication #20722
Comments
Any updates, please? This is breaking production setup |
Any updates on this please? |
MS Teams - please provide an update on this. This is very critical and I've been looking for an update since more or less a month. Earlier your support teams told me that because of deploy freeze the Product team won't be able to fix it before 6th January. Today is 7th January, can please get this escalated now? |
I am also experiencing this issue, this is related to a breaking change in the Azure CLI 30283. Would be great if this can get priority to get fixed |
MS Teams - Can we please get some traction on this task? Would appreciate if this can be prioritized? |
Hey @KKing299 , @bveldhuis can you create a new Azure Resource Management service connection using Workload Identity Federation and then use this new service connection with the task? |
Hi, |
@LeftTwixWand - Please understand that what you're saying partially works since Workload identity Federation doesn't use the same parameter. |
Correct, @xhoogland and I work together on this. |
New issue checklist
Task name
ARM template deployment
Task version
3.*
Issue Description
Same issue that we had with Azure CLI a few weeks back. ARM template deployment task needs to change the parameter "--password" with "certificate". Looks like ARM template deployment task utilizes AZ CLI for auth. That's where the issue is. Please read below the log.
We need this fixed ASAP! This is breaking all production pipelines.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-latest
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: