feature request to make --sku and --name optional for vmware extension
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
### Preconditions
- [X] No need to upgrade Python SDK or the Python SDK is ready.
### Related command
az vmware cluster create
Arguments
--**name** -n [Required] : Name of the cluster.
--private-cloud -c [Required] : Name of the private cloud.
--resource-group -g [Required] : Name of resource group. You can configure the default group
-- **SKU**
using az configure --defaults group=.
### Resource Provider
Microsoft.AVS/privateClouds
### Description of Feature or Work Requested
Currently automation parametrizes $SKU, from cloud properties using :
```
(az vmware private-cloud show -g RG-AVSAZ01 -n AVS-SDDC| convertfrom-json).sku
```
The problem is in cluster name parameter needed for command to create cluster:
```
(az vmware private-cloud show -g RG-AVSAZ01 -n AVS-SDDC| convertfrom-json).name
```
CAn we make that name consistent between Azure AVS properties and VMware properties?
When two different teams manage azure VMware Solution this bug in CLI presents high risk to delete wrong cluster due to inconsistency.
Solution would be for az vmware cluster create *not* be blocked by SKU or NAME
### Minimum API Version Required
Extensions: vmware 5.0.2
### Swagger PR link / SDK link
https://portal.microsofticm.com/imp/v3/incidents/details/335010837/home
### Request Example
_No response_
### Target Date
2023-09-01
### PM Contact
cataggar
### Engineer Contact
@deboeyna, @khensler, @benaohana
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.