You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I edit the rules using the Azure portal it allows the /legacy-login value. Running terraform plan will obviously see the change and try to roll it back, see output after the change done manually
│ Error: "conditions.0.url_path_condition.0.match_values.0" must not begin with the URLs leading slash(e.g. /), got "/legacy-login"
│
│ on test.tf line 16, in resource "azurerm_cdn_frontdoor_rule" "index":
│ 16: match_values = ["/legacy-login"]
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.104.0
Affected Resource(s)/Data Source(s)
azurerm_cdn_frontdoor_rule
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
It should be supported.
I found #21851, which fixes the issue when using just
/
. I believe the fix would be to remove this conditional block https://github.com/hashicorp/terraform-provider-azurerm/pull/22610/files#diff-e2d4895b125eec64059034bf8652c9c54638785ec2d6c8555d25b80bb9652350R49If I edit the rules using the Azure portal it allows the
/legacy-login
value. Running terraform plan will obviously see the change and try to roll it back, see output after the change done manuallyActual Behaviour
I get this error
Steps to Reproduce
terraform validate
Important Factoids
No response
References
/
/
:The text was updated successfully, but these errors were encountered: