Dns Zone (A, AAAA, CNAME) don't properly support targetResource

[knuijver]

Bicep version
Bicep CLI version 0.24.24 (5646341)

Describe the bug
I expected this to create an A-record in the DNS Zone with a Alias resource type and a Alias target
But is created an empty A-record without reference to the publicIPAddresses

To Reproduce
Steps to reproduce the behavior:

resource demoIp 'Microsoft.Network/publicIPAddresses@2023-06-01' = {
  name: 'demo-ip'
  location: location
  sku: {
     name: 'Basic'
     tier: 'Regional'
  }
  properties: {
    publicIPAllocationMethod: 'Dynamic'
    publicIPAddressVersion: 'IPv4'
  }
}

resource dnsZone 'Microsoft.Network/dnsZones@2023-07-01-preview' existing = {
  name: 'mydomain.com'
}

resource dnsRecord 'Microsoft.Network/dnsZones/A@2023-07-01-preview' = {
  name: 'demo'
  parent: dnsZone
  properties: {
    TTL: 300
    targetResource: demoIp
  }
}

Additional context
It is posible to configure this via the Azure Portal, the setup looks like this:
And the Public IP address is assigned to a Virtual network gateway.

In the Public DNS Zone

The Record:

Public IP address - Configuraion

in ARM the zone entry looks like:

      {
          "type": "Microsoft.Network/dnszones/A",
          "apiVersion": "2018-05-01",
          "name": "example.com/example",
          "dependsOn": [
              "[resourceId('Microsoft.Network/dnszones', 'example.com')]"
          ],
          "properties": {
              "TTL": 3600,
              "targetResource": {
                  "id": "/subscriptions/0000000-0000-0000-0000-000000000000/resourceGroups/Development/providers/Microsoft.Network/publicIPAddresses/demogwpip"
              }
          }
      },

[ahelland]

Hmmm. I didn't interpret the docs that way, but went with this:

resource dnsRecord 'Microsoft.Network/dnsZones/A@2023-07-01-preview' = {
  name: 'demo'
  parent: dnsZone
  properties: {
    TTL: 300
    ARecords: [
      {
        ipv4Address: '192.168.1.1'
      }
    ]
  }
}

If you try to create a record in the portal and insert the resource into VS Code targetResource will be empty: targetResource: {}

[knuijver]

I've added some details to Additional context of the issue
It is posible to configure this via the Azure Portal, the setup looks like this, and the Public IP address is assigned to a Virtual network gateway.

[alex-frankel]

This is just a guess, but it looks like targetResource: demoIp should instead be:

targetResource: {
  id: demoIp.id
}