Open
Description
Bicep version
Microsoft.Network/loadBalancers/inboundNatRules@2022-05-01
Bicep: Bicep CLI version 0.11.1 (030248d)
Describe the bug
Using the Portal and selecting "Azure Virtual Machine " option to create NAT rule results in (resources.azure.com):
{
"name": "ssh-tunnel-attempt2",
"id": "/subscriptions/###/resourceGroups/ds-edp-test/providers/Microsoft.Network/loadBalancers/###/inboundNatRules/ssh-tunnel-attempt2",
"etag": "W/\"570da290-0502-4c95-b006-160d66b305e9\"",
"type": "Microsoft.Network/loadBalancers/inboundNatRules",
"properties": {
"provisioningState": "Succeeded",
"frontendIPConfiguration": {
"id": "/subscriptions/###/resourceGroups/###/providers/Microsoft.Network/loadBalancers/###/frontendIPConfigurations/lb-pip-conf"
},
"frontendPort": 35555,
"backendPort": 22,
"enableFloatingIP": false,
"idleTimeoutInMinutes": 4,
"protocol": "Tcp",
"enableDestinationServiceEndpoint": false,
"enableTcpReset": false,
"allowBackendPortConflict": false,
"backendIPConfiguration": {
"id": "/subscriptions/###/resourceGroups/###/providers/Microsoft.Network/networkInterfaces/ssh-tunnel-nic/ipConfigurations/ipconfig1"
}
}
}Creating this in bicep seems to be impossible:
WARNING: C:\temp\buildStatusMaker\ssh-tunnel.bicep(217,5) : Warning BCP037: The property "backendIpConfiguration" is not allowed on objects of type "InboundNatRulePropertiesFormat". Permissible properties include "backendAddressPool", "enableFloatingIP", "enableTcpReset", "frontendPortRangeEnd", "frontendPortRangeStart", "idleTimeoutInMinutes". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
When the resource is deployed it is identical to the one created by the Portal, except the backendIPConfiguration property is missing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment