Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VMSize not recognised when it's in a variable (possible regression of #695) #726

Open
GeordieGuy opened this issue Jan 17, 2023 · 1 comment

Comments

@GeordieGuy
Copy link

The following Bicep;

`
var referenceImage = {
windows: {
publisher: 'MicrosoftWindowsServer'
offer: 'WindowsServer'
sku: '2019-Datacenter'
version: 'latest'
VMsize: 'Standard_D4s_v3'
}
}

.
.
.

resource ImageReferenceVM 'Microsoft.Compute/virtualMachines@2022-08-01' = {
name: 'prdaueimagevm01'
location: location
properties: {
hardwareProfile: {
vmSize: referenceImage.windows.VMsize
}
osProfile: {
computerName: 'prdaueimagevm01'
adminUsername: vmAdminUsername
adminPassword: vmAdminPassword
}
storageProfile: {
imageReference: {
publisher: referenceImage.windows.publisher
offer: referenceImage.windows.offer
sku: referenceImage.windows.sku
version: referenceImage.windows.version
}
osDisk: {
createOption: 'FromImage'
managedDisk: {
storageAccountType: 'StandardSSD_LRS'
}

`

Raises an error with the latest arm-ttk (0.22) that

VM Size for resourceType ' ' named ' ' must be a parameter

@ghost ghost added the Needs: triage 🔍 label Jan 17, 2023
@vidapour
Copy link

@GeordieGuy could you provide your full template Bicep AND full ARM template here so that we can test with them? Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants