Snippets should encourage use of symbolicName.id where possible instead of using resourceId

[StephenWeatherford]

For instance, the 'res-nic' snippet output is this:

resource networkInterface 'Microsoft.Network/networkInterfaces@2020-11-01' = {
  name: 'name'
  location: resourceGroup().location
  properties: {
    ipConfigurations: [
      {
        name: 'name'
        properties: {
          privateIPAllocationMethod: 'Dynamic'
          subnet: {
            id: resourceId('Microsoft.Network/virtualNetworks/subnets', 'virtualNetwork', 'subnet')
          }
        }
      }
    ]
  }
}

RECOMMEND:

resource networkInterface 'Microsoft.Network/networkInterfaces@2020-11-01' = {
  name: 'name'
  location: resourceGroup().location
  properties: {
    ipConfigurations: [
      {
        name: 'name'
        properties: {
          privateIPAllocationMethod: 'Dynamic'
          subnet: {
            id: subnet.id
          }
        }
      }
    ]
  }
}

Note that this does show an error since subnet is. not defined:

Another possibilty would be to show the dependencies as explicit 'existing' resources, e.g.:

resource vnet 'Microsoft.Network/virtualNetworks@2021-02-01' existing = {
  name: 'Virtual network'
}

resource subnet 'Microsoft.Network/virtualNetworks/subnets@2021-02-01' existing = {
  parent: vnet
  name: 'Subnet'
}

resource networkInterface 'Microsoft.Network/networkInterfaces@2020-11-01' = {
  name: 'name'
  location: resourceGroup().location
  properties: {
    ipConfigurations: [
      {
        name: 'name'
        properties: {
          privateIPAllocationMethod: 'Dynamic'
          subnet: {
            id: subnet::id
          }
        }
      }
    ]
  }
}

[bhsubra]

Pending:
res-loadbalancer-external.bicep
res-loadbalancer-internal.bicep
res-log-analytics-solution.bicep