search

worxspace / PSPulumi

GNU General Public License v3.0
7 stars 1 forks source link

New-AzureNativeComputeVirtualMachine: ValidateSet for hardwareProfile not correct #4

Closed janegilring closed 2 years ago

janegilring commented 2 years ago

I have Standard_D2s_v4 available in my subscription, but this isn`t available in the list used by ValidateSet:

MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Cannot process argument transformation on parameter
'hardwareProfile'. Cannot create object of type "HardwareProfile". The argument "Standard_D2s_v4" does
not belong to the set
"Basic_A0,Basic_A1,Basic_A2,Basic_A3,Basic_A4,Standard_A0,Standard_A1,Standard_A2,Standard_A3,Standard_A
4,Standard_A5,Standard_A6,Standard_A7,Standard_A8,Standard_A9,Standard_A10,Standard_A11,Standard_A1_v2,S
tandard_A2_v2,Standard_A4_v2,Standard_A8_v2,Standard_A2m_v2,Standard_A4m_v2,Standard_A8m_v2,Standard_B1s
,Standard_B1ms,Standard_B2s,Standard_B2ms,Standard_B4ms,Standard_B8ms,Standard_D1,Standard_D2,Standard_D
3,Standard_D4,Standard_D11,Standard_D12,Standard_D13,Standard_D14,Standard_D1_v2,Standard_D2_v2,Standard
_D3_v2,Standard_D4_v2,Standard_D5_v2,Standard_D2_v3,Standard_D4_v3,Standard_D8_v3,Standard_D16_v3,Standa
rd_D32_v3,Standard_D64_v3,Standard_D2s_v3,Standard_D4s_v3,Standard_D8s_v3,Standard_D16s_v3,Standard_D32s
_v3,Standard_D64s_v3,Standard_D11_v2,Standard_D12_v2,Standard_D13_v2,Standard_D14_v2,Standard_D15_v2,Sta
ndard_DS1,Standard_DS2,Standard_DS3,Standard_DS4,Standard_DS11,Standard_DS12,Standard_DS13,Standard_DS14
,Standard_DS1_v2,Standard_DS2_v2,Standard_DS3_v2,Standard_DS4_v2,Standard_DS5_v2,Standard_DS11_v2,Standa
rd_DS12_v2,Standard_DS13_v2,Standard_DS14_v2,Standard_DS15_v2,Standard_DS13-4_v2,Standard_DS13-2_v2,Stan
dard_DS14-8_v2,Standard_DS14-4_v2,Standard_E2_v3,Standard_E4_v3,Standard_E8_v3,Standard_E16_v3,Standard_
E32_v3,Standard_E64_v3,Standard_E2s_v3,Standard_E4s_v3,Standard_E8s_v3,Standard_E16s_v3,Standard_E32s_v3
,Standard_E64s_v3,Standard_E32-16_v3,Standard_E32-8s_v3,Standard_E64-32s_v3,Standard_E64-16s_v3,Standard
_F1,Standard_F2,Standard_F4,Standard_F8,Standard_F16,Standard_F1s,Standard_F2s,Standard_F4s,Standard_F8s
,Standard_F16s,Standard_F2s_v2,Standard_F4s_v2,Standard_F8s_v2,Standard_F16s_v2,Standard_F32s_v2,Standar
d_F64s_v2,Standard_F72s_v2,Standard_G1,Standard_G2,Standard_G3,Standard_G4,Standard_G5,Standard_GS1,Stan
dard_GS2,Standard_GS3,Standard_GS4,Standard_GS5,Standard_GS4-8,Standard_GS4-4,Standard_GS5-16,Standard_G
S5-8,Standard_H8,Standard_H16,Standard_H8m,Standard_H16m,Standard_H16r,Standard_H16mr,Standard_L4s,Stand
ard_L8s,Standard_L16s,Standard_L32s,Standard_M64s,Standard_M64ms,Standard_M128s,Standard_M128ms,Standard
_M64-32ms,Standard_M64-16ms,Standard_M128-64ms,Standard_M128-32ms,Standard_NC6,Standard_NC12,Standard_NC
24,Standard_NC24r,Standard_NC6s_v2,Standard_NC12s_v2,Standard_NC24s_v2,Standard_NC24rs_v2,Standard_NC6s_
v3,Standard_NC12s_v3,Standard_NC24s_v3,Standard_NC24rs_v3,Standard_ND6s,Standard_ND12s,Standard_ND24s,St
andard_ND24rs,Standard_NV6,Standard_NV12,Standard_NV24" specified by the ValidateSet attribute. Supply
an argument that is in the set and then try the command again."
rdbartram commented 2 years ago

resolved in #5 module version 0.0.3

basically, since we don't want to have to force you to always download the modules, and we cant guarantee that schema we use has all the types, we are switching to argumentcompletions, what this means is that we don't enforce the use of the values, but we offer them in the IDE when coding. We realise this could lead to issues as mistakes are not caught at build time, but it provides the best support.

If anyone has any ideas, how we can better fix this, let us know.