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
Sorry to bring the bad news but it seems there is another issue:
cdn.EndpointsClient#Create: Failure sending request:
StatusCode=400 -- Original Error: Code="BadRequest"
Message="We couldn’t configure QueryStringCachingBehavior, IsCompressionEnabled, ContentTypesToCompress, GeoFilters and DeliveryPolicy for premium profile endpoints.
You’ll need to manage these endpoints in the supplemental portal."
The terraform provider seems to add the QueryStringCachingBehavior and ContentTypesToCompress by default like IsCompressionEnabled was before the PR.
Added test for "Premium_Verizon" SKU for azurerm_cdn_profile
Assigning the parameters EndpointProperties.ContentTypesToCompress, EndpointProperties.GeoFilters only when values are set for content_types_to_compress, geo_filter.
Assigning the parameter EndpointProperties.DeliveryPolicy only when SKU set to Microsoft_Standard.
Fixes#9895
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Jan 27, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry to bring the bad news but it seems there is another issue:
The terraform provider seems to add the QueryStringCachingBehavior and ContentTypesToCompress by default like IsCompressionEnabled was before the PR.
eg:
Seems like the tests of the provider are not really in Sync with API. Especially with the verizon API.
Originally posted by @zekth in #1109 (comment)
The text was updated successfully, but these errors were encountered: