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
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.
The text was updated successfully, but these errors were encountered:
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
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 and limited conversation to collaborators
Jun 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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."
The text was updated successfully, but these errors were encountered: