-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
az deployment group create: mode is not a known attribute of class... #26112
Comments
Thank you for opening this issue, we will look into it. |
In fact, this issue is caused by the lack of
Since I did not find a record of mode attribute being removed in the history notes of Python SDK, I am not sure if there was a breaking change in the Python SDK/Swagger which was not recorded in the history notes or if this was a bug with the previous code.As template spec related code is owned by service team, + @detienne20 to help take a look at this issue
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft. Issue DetailsThis is autogenerated. Please review and update as needed.Describe the bugCommand Name Errors:
It breaks our pipelines. Why is a warning written to standard error? To Reproduce:
Expected Behavior
Environment Summary
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/deployments-owners. Issue DetailsThis is autogenerated. Please review and update as needed.Describe the bugCommand Name Errors:
It breaks our pipelines. Why is a warning written to standard error? To Reproduce:
Expected Behavior
Environment Summary
|
@zhoxing-ms I can't see any evidence of this property ever having been here - here's the |
@anthony-c-martin Thank you for your clarification. Since the |
Why removing? Does this imply that something is wrong regarding mode on our side? |
Yes, I guess this was a legacy code issue. @detienne20 please help confirm it~ |
At a first glance we don't set any mode in that regard. Is this maybe something happening under the cover which is hidden from us? |
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az deployment group create
Errors:
It breaks our pipelines. Why is a warning written to standard error?
With 2.46.0 everything was healthy.
To Reproduce:
az deployment group create --name "" --resource-group "" --template-spec "" --parameters ""
Expected Behavior
Environment Summary
The text was updated successfully, but these errors were encountered: