Open MarsWangyang opened 1 year ago
Thank you for opening this issue, we will look into it.
Is this related to https://github.com/Azure/bicep-types-az/issues/1660 ?
@johnnyreilly Essentially yes, they also use 2022-10-01 version in AzCLI right now, which ran into the same problem as yours. I'm just afraid they might forget not only in bicep but also in AzCLI 😅
It's probably a common underlying dependency I guess - though I note @JFolberth reported general issues with 2023-05-01 so I wonder if there's other problems
Adding Service team to look into this.
Describe the bug
The command is calling API version with 2022-10-01, which will break the setting of capacity to "Should be null" error when setting the
--scale-type "Standard"
. However, if I change the API version to 2023-05-01, the problem will be fixed though using RESTful API to change or update the capacity of AOAI model from 120 TPM (Token-Per-Minute) in default to others.Related command
or
Errors
... cli.azure.cli.core.azclierror: (InvalidCapacity) The capacity should be null for standard deployment. Code: InvalidCapacity Message: The capacity should be null for standard deployment. az_command_data_logger: (InvalidCapacity) The capacity should be null for standard deployment. Code: InvalidCapacity Message: The capacity should be null for standard deployment. ...
Issue script & Debug output
Expected behavior
The command should change the capacity (120 TPM in default) to the integer the user put in. e.g. 120TPM --> 150 TPM
Environment Summary
azure-cli 2.50.0
core 2.50.0 telemetry 1.0.8
Extensions: aks-preview 0.5.145 appservice-kube 0.1.8 azure-devops 0.26.0 azure-firewall 0.14.8 connectedk8s 1.3.20 containerapp 0.3.35 customlocation 0.1.3 interactive 0.5.1 k8s-extension 1.4.2 log-analytics 0.2.2 spring 1.14.0 spring-cloud 3.1.8 ssh 1.1.6
Dependencies: msal 1.22.0 azure-mgmt-resource 23.1.0b2
Additional context