Support for new SKUs in azurerm_express_route_circuit

[janegilring]

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 "+1" or "me too" comments, 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

Description

ExpressRoute has a new tier called Local. This is not visible in the Azure portal yet, but can be created directly via the API, Azure CLI or Azure PowerShell. It is documented in the help for the CLI (az network express-route create --help):

--sku-tier                     : SKU Tier of ExpressRoute circuit.  Allowed values: Basic,
                                 Local, Premium, Standard.  Default: Standard.

This SKU should be added as a valid value in the Terraform provider.

New or Affected Resource(s)

• azurerm_express_route_circuit (affected)

Potential Terraform Configuration

resource "azurerm_resource_group" "example" {
  name     = "exprtTest"
  location = "West US"
}

resource "azurerm_express_route_circuit" "example" {
  name                  = "expressRoute1"
  resource_group_name   = "${azurerm_resource_group.example.name}"
  location              = "${azurerm_resource_group.example.location}"
  service_provider_name = "Equinix"
  peering_location      = "Silicon Valley"
  bandwidth_in_mbps     = 50

  sku {
    tier   = "Local"
    family = "MeteredData"
  }

  tags = {
    environment = "Production"
  }
}

[neil-yechenwei]

It seems that it failed to create with your above tf config. Could you share a valid tf config for new tier "Local"?

The error message: Error: Error Creating/Updating ExpressRouteCircuit "expressRoute1" (Resource Group "exprtTest"): Code="InvalidParameter" Message="Circuit Sku \"Basic\" is not allowed on Provider Entity Equinix." Details=[]

on main.tf line 6, in resource "azurerm_express_route_circuit" "example": 6: resource "azurerm_express_route_circuit" "example" {

[janegilring]

I would expect it to fail since Local is not an accepted SKU in the Terraform provider, the configuration was meant as an example on how it should/could look like when that support is implemented.

On a related note, we have a support case going with Microsoft since we had issues enabling the Local SKU from the Azure CLI as well. This morning we got the following information:

We have received update from our Product Group that the Express Route Local feature has been disabled temporarily for all locations. The plan is to enable it back but it might take another 2 weeks. I have also informed them that the documents are not updated with this information. Please accept our apologies for the inconvenience caused due to this.

[neil-yechenwei]

Could you share your Azure CLI command with new tier Local since I am not sure which provider and peering location allows new tier Local?

[janegilring]

Sure, this is the command we ran: az network express-route create --bandwidth 2000 -n expressroute-local --peering-location Oslo -g networking-rg --provider "Telenor Secure Cloud Connect" -l "Norway East" --sku-family MeteredData --sku-tier Local

[pearcec]

@tracypholmes Looks like this has been merged and is in v2.6.0, but it was never tagged for the CHANGELOG. Can we close this out?

[favoretti]

Since this issue seems to have been addressed in the latest versions of the provider (or a valid workaround was provided) - I'm going to close it. Please open a new updated bug report if this is still relevant. Thank you.

[github-actions[bot]]

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.