azurerm_cdn_profile SKU is not up to date

[DuyTran-TomTom]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

CDN Standard/Premium Verizon is no longer an option for Azure CDN. They have been renamed to Standard/Premium Edgio.

Azure CDN Standard/Premium from Verizon has been renamed to Azure CDN Standard/Premium from Edgio and this change was from Verizon.

Refer: https://meet.edg.io/blog/verizon/

See this accepted answer from Microsoft Support: https://learn.microsoft.com/en-us/answers/questions/1431325/is-azure-verizon-cdn-being-retired

The azurerm_cdn_profile resource still has the old options for SKU

sku - (Required) The pricing related information of current CDN profile. Accepted values are Standard_Akamai, Standard_ChinaCdn, Standard_Microsoft, Standard_Verizon or Premium_Verizon. Changing this forces a new resource to be created.

Standard_Akamai is also deprecated. These values should be updated to match with the new changes.

New or Affected Resource(s)/Data Source(s)

azurerm_cdn_profile

Potential Terraform Configuration

No response

References

No response

[Chambras]

Nice catch @DuyTran-TomTom
I will do some research on it.

[pr0b3r7]

Hi @Chambras - any updates?

[Techbrunch]

Is there a workaround currently to use Edgio with Terraform ?

[richard-sistern]

The following SKUs are supported

Custom_Verizon'
'Premium_AzureFrontDoor'
'Premium_Verizon'
'StandardPlus_955BandWidth_ChinaCdn'
'StandardPlus_AvgBandWidth_ChinaCdn'
'StandardPlus_ChinaCdn'
'Standard_955BandWidth_ChinaCdn'
'Standard_Akamai'
'Standard_AvgBandWidth_ChinaCdn'
'Standard_AzureFrontDoor'
'Standard_ChinaCdn'
'Standard_Microsoft'
'Standard_Verizon'
Source: https://learn.microsoft.com/en-us/azure/templates/microsoft.cdn/profiles?pivots=deployment-language-terraform#sku-2

Looks like Edgio is on it's way out though https://learn.microsoft.com/en-us/azure/cdn/edgio-retirement-faq

[lra]

Same issue here. We were forced to upgrade from Standard_Verizon to Standard_AzureFrontDoor and the terraform provider does not support it.

Plan does:

~ sku                 = "Standard_AzureFrontDoor" -> "Standard_Verizon" # forces replacement

But if we set the sku to "Standard_AzureFrontDoor" we get this error:

│ Error: expected sku to be one of ["Standard_Akamai" "Standard_ChinaCdn" "Standard_Verizon" "Standard_Microsoft" "Premium_Verizon"], got Standard_AzureFrontDoor
│
│   with azurerm_cdn_profile.obie_cdn,
│   on cdn.tf line 11, in resource "azurerm_cdn_profile" "obie_cdn":
│   11:   sku                 = "Standard_AzureFrontDoor"

So we are stuck, latest version of everything:

Terraform v1.10.4
on darwin_arm64
+ provider registry.terraform.io/hashicorp/azurerm v4.15.0

[richard-sistern]

Same issue here. We were forced to upgrade from Standard_Verizon to Standard_AzureFrontDoor and the terraform provider does not support it.

Plan does:

~ sku                 = "Standard_AzureFrontDoor" -> "Standard_Verizon" # forces replacement

But if we set the sku to "Standard_AzureFrontDoor" we get this error:

│ Error: expected sku to be one of ["Standard_Akamai" "Standard_ChinaCdn" "Standard_Verizon" "Standard_Microsoft" "Premium_Verizon"], got Standard_AzureFrontDoor
│
│   with azurerm_cdn_profile.obie_cdn,
│   on cdn.tf line 11, in resource "azurerm_cdn_profile" "obie_cdn":
│   11:   sku                 = "Standard_AzureFrontDoor"

So we are stuck, latest version of everything:

Terraform v1.10.4
on darwin_arm64
+ provider registry.terraform.io/hashicorp/azurerm v4.15.0

You can use azurerm_cdn_frontdoor_profile as a replacement.

[lra]

You can use azurerm_cdn_frontdoor_profile as a replacement.

Thanks!, that works.