-
Notifications
You must be signed in to change notification settings - Fork 3k
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
New version of AZ CLI (2.27.0) Is Not Usable when using what-if command #19124
Comments
This is breaking production deployment! |
We're having the same issue - if there are no changes reported by the what-if command, the AZ CLI returns ERROR: 'NoEffect' |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure. Issue DetailsNew version of AZ CLI (2.27.0) is not usable, getting error ERROR: 'NoEffect' To Reproduce Note: 2.26.0 is working fine, no issue. Expected behavior Environment summary
|
route to service team |
@shenglol Could you please take a look at this issue? |
Also affected by this. Working around with try/catch in automation.... But a NoEffect change should be at most a Warning, not an Error. |
I'm having the same issues in our PRD environment. @Gordonby do you mind sharing your try/catch solution? I tried this but failed. My PS knowledge is not up to the level I wish it was :) |
Fixed in Azure CLI 2.27.1 |
@shenglol |
@Qi-Jian-Huang-DevOps Apologies for the late reply. Could you please let us know if you are still facing this issue with |
yup, latest azCLI resolves the issue, thanks. |
New version of AZ CLI (2.27.0) is not usable, getting error
ERROR: 'NoEffect'
To Reproduce
Update your AZ CLI to latest (2.27.0), then run a what-if deployment such as
az deployment sub what-if -f ..
Note: 2.26.0 is working fine, no issue.
Expected behavior
Expected to run what-if with no problem
Environment summary
Latest microsoft hosted windows agent
AZ CLI 2.27.0
The text was updated successfully, but these errors were encountered: