[AVM Module Issue]: VMSS Module extensionHealthConfig settings gets reverted to default on deployment

[bawenna]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/compute/virtual-machine-scale-set

(Optional) Module Version

0.6.0

Description

For the settings in extensionHealthConfig, no matter what I values I put in for the port, protocol and request path, it always get reverted to the default one showing in the example. For example I have
extensionHealthConfig: {
enabled: true
settings: {
port: 443
protocol: 'https'
requestPath: '/path'
}
}
in my bicep, once I deploy it out, it reverts back to
{
"protocol": "http",
"port": 80,
"requestPath": "/"
}
I am trying to deploy the health extension that checks a different request path other than /, is there a way around this?

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@bawenna, thanks for submitting this issue for the avm/res/compute/virtual-machine-scale-set module!

Important

A member of the @Azure/avm-res-compute-virtualmachinescaleset-module-owners-bicep or @Azure/avm-res-compute-virtualmachinescaleset-module-contributors-bicep team will review it soon!