freezing-memory-87554
05/24/2021, 12:50 PMworried-knife-31967
05/24/2021, 2:22 PMfreezing-memory-87554
05/24/2021, 2:28 PMworried-knife-31967
05/24/2021, 2:28 PMfreezing-memory-87554
05/24/2021, 2:31 PMworried-knife-31967
05/24/2021, 2:31 PMtall-librarian-49374
05/24/2021, 5:51 PMworried-knife-31967
05/24/2021, 7:32 PMfreezing-memory-87554
05/24/2021, 7:51 PMHealthProbeSettings =
{
new AzureNative.Network.Inputs.HealthProbeSettingsModelArgs
{
EnabledState = "Enabled",
HealthProbeMethod = "HEAD",
IntervalInSeconds = 120,
Name = "healthProbeSettings1",
Path = "/",
Protocol = "Http",
},
}
and apparently this settings should be referenced in BackendPoolArgs as:
HealthProbeSettings = new AzureNative.Network.Inputs.SubResourceArgs
{
Id = "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.Network/frontDoors/frontDoor1/healthProbeSettings/healthProbeSettings1",
},
I found no resource in Pulumi SDK which allows one to create HealthProbeSettings separately from FrontDoor. The same goes for:
LoadBalancingSettings
FrontendEndpoints in RoutingRuleArgs
BackendPool in ForwardingConfigurationArgs
etc.
tall-librarian-49374
05/25/2021, 5:49 AMThat’s being presented as SubResourceArgs for the healthprobe.There’s a
HealthProbeSettings
property with full arguments, as @freezing-memory-87554 shows above.I found no resource in Pulumi SDK which allows one to create HealthProbeSettings separately from FrontDoor.Yeah, because those resources do not exist in ARM API.
freezing-memory-87554
05/25/2021, 7:53 AM{
"type": "Microsoft.Network/frontdoors/frontendEndpoints/customHttpsConfiguration",
"apiVersion": "2020-07-01",
"name": "[concat(parameters('frontDoorName'), '/frontendEndpoint2/default')]",
"dependsOn": [
"[parameters('frontDoorName')]"
],
"properties": {
"protocolType": "ServerNameIndication",
"certificateSource": "FrontDoor",
"frontDoorCertificateSourceParameters": {
"certificateType": "Dedicated"
},
"minimumTlsVersion": "1.2"
}
}
worried-knife-31967
05/25/2021, 8:16 AMfreezing-memory-87554
05/25/2021, 8:59 AMtall-librarian-49374
05/25/2021, 12:04 PMfreezing-memory-87554
05/25/2021, 12:04 PMtall-librarian-49374
05/25/2021, 12:06 PMthat there’s a reluctance to provide an example for an obscure setup like that.We do have one example https://www.pulumi.com/docs/reference/pkg/azure-native/network/frontdoor/ But again, we rely on ARM here and expose examples that Microsoft highlighted in their specs.
freezing-memory-87554
05/25/2021, 12:16 PMtall-librarian-49374
05/25/2021, 12:16 PM2020-07-01
isn’t published at all… https://github.com/Azure/azure-rest-api-specs/tree/master/specification/frontdoor/resource-manager/Microsoft.Network/stableAt least for me it completely doesn’t work. Deployment succeeds but this section simply being ignored. HTTP continues to be disabled
This did work briefly at the start, but definitely not consistently
freezing-memory-87554
05/25/2021, 12:27 PMtall-librarian-49374
05/25/2021, 12:33 PMEnableHTTPS
POST endpointworried-knife-31967
05/25/2021, 6:15 PMtall-librarian-49374
05/25/2021, 6:47 PM