Open AmberYangY opened 1 year ago
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.
Author: | AmberYangY |
---|---|
Assignees: | zhoxing-ms |
Labels: | `bug`, `Service Attention`, `ARM`, `customer-reported`, `Auto-Assign`, `Azure CLI Team` |
Milestone: | Backlog |
Since this error message was returned by the REST service, it needs the ARM service team to see if the REST supports Complete
mode. Please note that the relevant documentation doc link states that it is supported.
Thanks for your reply.
May I know is it possible to transfer/merge this GitHub issue to the GitHub page managed by ARM team?
Since this error message was returned by the REST service, it needs the ARM service team to see if the REST supports
Complete
mode. Please note that the relevant documentation doc link states that it is supported.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/deployments-owners.
Author: | AmberYangY |
---|---|
Assignees: | zhoxing-ms |
Labels: | `bug`, `Service Attention`, `ARM - Templates`, `customer-reported`, `Auto-Assign`, `Azure CLI Team` |
Milestone: | Backlog |
Complete mode is not a valid mode for non-RG scoped deployments. Is "Complete" a current valid enum for this property?
@alex-frankel Hi Alex, may I know will you help to raise any work item to update the REST API doc with the correct swagger spec?
https://msazure.visualstudio.com/One/_workitems/edit/24640447
Does this work item need to be finished in order to resolve this CLI issue? I don't believe these CLI commands are auto-generated. If that is the case, someone will need to create the PR on the CLI side, is that right?
@zhoxing-ms since the root cause of this is a swagger inaccuracy, please could you move this to https://github.com/Azure/azure-rest-api-specs?
since the root cause of this is a swagger inaccuracy, please could you move this to https://github.com/Azure/azure-rest-api-specs?
@anthony-c-martin Sorry, our team is not responsible for this repo. Could you please directly create a new issue on that repo and copy the content of this issue to it?
This is still broken -> ERROR: {"code": "InvalidDeployment", "message": "Specified deployment mode 'Complete' is not supported for deployment at the current scope. Please see https://aka.ms/deployment-modes for usage details."}
Describe the bug
From the following doc, az deployment mg create should support [--mode {Complete, Incremental}]. https://learn.microsoft.com/en-us/cli/azure/deployment/mg?view=azure-cli-latest#az-deployment-mg-create But I tested it from my side, the error message mentioned the deployment mode "complete" is not supported for the management group scope.
Related command
az deployment mg create --location WestUS --management-group-id xxx --name xxx --template-file "xxx"
Errors
{"code": "InvalidDeployment", "message" : "Specified deployment mode 'Complete' is not supported for deployment at the current scope. Please see https://aka.ms/deployment-modes for usage details."}
Issue script & Debug output
az deployment mg create --location WestUS --management-group-id xxx --name xxx --template-file "xxx"
Expected behavior
The deployment should be handled with Complete mode.
Environment Summary
azure-cli 2.50.0
Additional context
No response