-
Notifications
You must be signed in to change notification settings - Fork 3.4k
feature request to make --sku and --name optional for vmware extension #27009
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botConfigureaz configure/configaz configure/configService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.feature-requestneeds-team-attentionThis issue needs attention from Azure service team or SDK teamThis issue needs attention from Azure service team or SDK team
Milestone
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botConfigureaz configure/configaz configure/configService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.feature-requestneeds-team-attentionThis issue needs attention from Azure service team or SDK teamThis issue needs attention from Azure service team or SDK team
Preconditions
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 :
The problem is in cluster name parameter needed for command to create cluster:
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