Open michaelrucker opened 2 months ago
I have a similar problem: receiving error message "the 'cdn_frontdoor_secret_id' field is not supported if the 'certificate_type' is 'ManagedCertificate'" when attempting to modify a custom domain's "min_tls_ver" property from "TLS12" to "TLS10" or vice versa.
In my use case, the custom domain is the only one defined in the Azure Front-Door profile and is using an Azure-managed certificate (property "certificate_type" = "ManagedCertificate").
Property "min_tls_ver" can be modified in the Azure Portal or using an Azure CLI command.
Is there an existing issue for this?
Community Note
Terraform Version
1.8.5
AzureRM Provider Version
3.109.0
Affected Resource(s)/Data Source(s)
azurerm_cdn_frontdoor_custom_domain
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
An azurerm_cdn_frontdoor_custom_domain that does not supply a fd-custom-domain-certificate-id should be created with a ManagedCertificate.
Actual Behaviour
An azurerm_cdn_frontdoor_custom_domain that does not supply a fd-custom-domain-certificate-id will not apply with an error that the cdn_frontdoor_secret_id field is not supported.
Steps to Reproduce
I am trying to create multiple azurerm_cdn_frontdoor_custom_domain resources that differ in the "tls" block of their configuration. Some will use certificate_type = "CustomerCertificate" and some will use certificate_type = "ManagedCertificate".
When certificate_type is set to "CustomerCertificate" you must also supply a cdn_frontdoor_secret_id. When certificate_type is set to "ManagedCertificate" you must not supply a cdn_frontdoor_secret_id.
To accomplish that I have tried using two dynamic tls blocks, one for each case, but even when the dynamic block being used does not contain the cdn_frontdoor_secret_id field the apply fails with the error provided.
Important Factoids
No response
References
No response