Output Array Not Valid

[Vegas588]

Hello,

Trying to output the subnet Ids and Names here and clearly my construct is wrong. Any help appreciated.

The template output 'snetIds' is not valid. The language expression property 'name' doesn't exist, available properties are 'snetPrefix'..

var subnets = [
  {
    snetPrefix: '10.0.0.0/28'
  }
  {
    snetPrefix: '10.0.0.16/28'
  }
  {
    snetPrefix: '10.0.0.32/28'
  }
  {
    snetPrefix: '10.0.0.48/28'
  }
]

resource vnet 'Microsoft.Network/VirtualNetworks@2020-07-01' = {
  name: toLower('${baseName}-${vnetSuffix}-1')
  location: location
  tags: resourceTags
  properties: {
    addressSpace: {
      addressPrefixes: [
        vnetAddressSpace
      ]
    }
    subnets: [for (subnet, i) in subnets: {
      name: toLower('${baseName}-${snetSuffix}-${i + 1}')
      properties: {
        addressPrefix: subnet.snetPrefix
      }
    }]
  }
}

output vnetId string = vnet.id //output resourceId of vnet
output snetIds array = [for subnet in subnets: {
  subName: subnet.name
  subId: subnet.Id
}]

[anthony-c-martin]

Note that subnets refers to your variable array, whose objects don't contain properties named "name" or "Id".

I think you just need to replace:

output snetIds array = [for subnet in subnets: {
  subName: subnet.name
  subId: subnet.Id
}]

With:

output snetIds array = [for subnet in vnet.properties.subnets: {
  subName: subnet.name
  subId: subnet.id
}]

[anitian-mkimball]

I think you have a couple of things going on.

1. ARM doesn't like a 'reference' function when used in a 'count' parameter in an iterative output. Bicep puts a 'reference' function in that count when you loop over a resource.
2. I don't believe iterative outputs are currently supported in bicep (link).

Here's a workaround that doesn't make me extremely happy. It equates the length of the "subnets" array with the number of subnets in the vnet, this doesn't have to be true. In this case it does happen to be true.

output snetIds array = [for i in range(0,length(subnets)): {
  subName: vnet.properties.subnets[i].name
  subId: vnet.properties.subnets[i].id
}]

I ran it on my subscription, it seems to behave as expected.

[alex-frankel]

@anitian-mkimball's solution is the right one. Just to add, we should have caught the failed cases in the VS Code extension prior to the code being deployed.

[Vegas588]

@anitian-mkimball Thanks so much! Would not have been able to determine this outcome. learning...
It did work for me as well.

The idea here is to take the subnets and be able to reference the Id in another module. So based on the info provided, I would reference the output as such?

modvnet: {
id: modvnet.outputs.subId[1]
}

[anitian-mkimball]

If I'm following correctly, I would get access to that module's output with something like:

modvnet.outputs.snetIds[1].subId

In this case, I'm grabbing the value of "subId" from the object at index 1 in the snetIds array that was outputted by the module that was named "modvnet".

Grabbing output data is well documented in the modules page of the docs (link).

If I'm not following correctly and this is all obvious to you, then I apologize and I'm going to need more info. Also, I haven't run that through a test, so forgive my syntax failures if they're there and let me know if it works or not.

[anthony-c-martin]

@anitian-mkimball, thanks for providing the fixed code! I've raised #2090 for the missing Bicep validation.

[Vegas588]

Initial question answered by @anitian-mkimball