Question on missing properties for bicep resource (Microsoft.Resources/deployments)

[kevball2]

Wanted to confirm an issue I was seeing.

Creating a resource object but missing some properties in the bicep IntelliSense. Is this due to an issue with the ARM API?

From ARM microsoft.resources/deployments

The resourceGroup property is unavailable in bicep. From the deploymentproperties-object the template property is not available as well though templatelink does work.

I was trying to convert the following ARM code over the bicep -

"properties": { 
                "mode": "Incremental",
                "template": {
                    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
                    "contentVersion": "1.0.0.0",
                    "resources": [
                        {
                            "type": "Microsoft.Network/virtualNetworks/subnets",
                            "apiVersion": "2019-09-01",
                            "name": "[concat(parameters('vnetName'), '/', parameters('subnetName'))]",
                            "properties": "[if(and(equals(parameters('subnetOption'), 'existing'), not(equals(parameters('privateEndpointType'), 'none'))), union(reference(variables('subnet'), '2019-09-01'), variables('subnetPolicyForPE')), json('null'))]"
                        }
                    ]
                }

I am guessing it is something with how bicep gets properties for the ARM templates correct? Is it something that Microsoft would have to fix?

Really liking the bicep language so far keep up the great work!

[alex-frankel]

In general, if a property is missing from intellisense, it is because the swagger that defines the contract of the REST API is inaccurate in some way.

However, for this particular example, we have an issue with our type generation system that missed the subscription and resourceGroup properties of the microsoft.resources/deployments resource. We have issue #145 tracking the fix, which should be done before 0.3 releases.

You also may be able to accomplish this with modules (doc) which have a scope property that will allow you to target another resource group:
https://github.com/Azure/bicep/blob/main/docs/spec/modules.md#defining-and-configuring-module-scopes

[kevball2]

In general, if a property is missing from intellisense, it is because the swagger that defines the contract of the REST API is inaccurate in some way.

However, for this particular example, we have an issue with our type generation system that missed the subscription and resourceGroup properties of the microsoft.resources/deployments resource. We have issue #145 tracking the fix, which should be done before 0.3 releases.

You also may be able to accomplish this with modules (doc) which have a scope property that will allow you to target another resource group:
https://github.com/Azure/bicep/blob/main/docs/spec/modules.md#defining-and-configuring-module-scopes

Thanks Alex,
For now, I just omitted that section of the ARM template that I was converting. I'll watch the #145 issue and try adding in the section again once that one is resolved.

[alex-frankel]

Closing now that #145 is done