Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expressroute bandwidth reduction doesn't de-provision and re-provision circuit as would be expected #3983

Closed
hawk0013 opened this issue Jul 31, 2019 · 2 comments · Fixed by #6601

Comments

@hawk0013
Copy link

When changing bandwidth_in_mbps to a value less than the currently provisioned amount, Terraform should deprovisioned and reprovisioned the circuit. Currently it will just try to directly change bandwidth_in_mbps and of course would fail, due to limitations described below.

https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager
"Although you can seamlessly upgrade the bandwidth, you cannot reduce the bandwidth of an ExpressRoute circuit without disruption. Downgrading bandwidth requires you to deprovision the ExpressRoute circuit and then reprovision a new ExpressRoute circuit."

@hawk0013 hawk0013 changed the title Expressroute bandwidth downgrade doesn't delete and re-create circuit as expected Expressroute bandwidth reduction doesn't de-provision and re-provision circuit as would be expected Jul 31, 2019
pearcec pushed a commit to pearcec/terraform-provider-azurerm that referenced this issue Apr 24, 2020
Reduction in bandwidth forces new resource, utilizing CustomizeDiff
tombuildsstuff pushed a commit to pearcec/terraform-provider-azurerm that referenced this issue May 7, 2020
Reduction in bandwidth forces new resource, utilizing CustomizeDiff
@katbyte katbyte added this to the v2.10.0 milestone May 13, 2020
katbyte pushed a commit that referenced this issue May 13, 2020
… when changing bandwidth reduction (#3983) (#6601)

Reduction in bandwidth forces new resource, utilizing CustomizeDiff

Fixes #3983
@ghost
Copy link

ghost commented May 15, 2020

This has been released in version 2.10.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.10.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Jun 13, 2020

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 ghost locked and limited conversation to collaborators Jun 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants