Azure / Azure/bicep-types-az

virtualMachineScaleSets health probe reference id

Open
#2,250 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

inaccuracy
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

Resource Type

Microsoft.Compute/virtualMachineScaleSets

Api Version

2024-03-01

Issue Type

Resource fails to deploy

Other Notes

https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/vmss-automatic-repairs-slb-health-probe/azuredeploy.json#L257
https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade#configuring-a-custom-load-balancer-probe-as-application-health-probe-on-a-scale-set

All the variations below, which are show in the docs above, get translated to this in the deployed arm template:
"networkProfile": {
"healthProbe": "[reference(resourceId('Microsoft.Network/loadBalancers', variables('lbName')), '2024-01-01').probes[1].id]",

Error in azure deployment: "Value for reference id is missing. Path Properties.UpdateGroups[0].NetworkProfile.healthProbe."

The warning shown by the linter: The property "healthProbe" expected a value of type "ApiEntityReference | null" but the provided value is of type "string".

Bicep Repro

networkProfile: {
healthProbe: lb.properties.probes[1].id
//'${lb.id}/probes/${lbProbeName443}'
//resourceId('Microsoft.Network/loadBalancers/probes', lbName, lbProbeName443)

Confirm
  • I have read the troubleshooting guide and looked for duplicates.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked azuredeploy.json around line 257 and compare its healthProbe reference with the Bicep repro and the linked Azure documentation. Confirm the expected reference-id shape and verify that the deployment no longer reports a missing reference id or the linter type warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.