-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Express Route Circuit (Microsoft Peering) Missing Arguments. #1084
Comments
This is still an issue.
Currently unable to configure peerings as I receive the following error message:
if the |
So looks like the following are missing? I will take a look at adding them. |
Fixing issue hashicorp#1084 Microsoft Peering is missing customer_asn and routing_registry_name - Test included - Website updated
This has been released in version 2.8.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.8.0"
}
# ... other configuration ... |
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! |
Terraform Version
0.11.6
Affected Resource(s)
express_route_circuit_pering (Microsoft Peering)
Terraform Configuration Files
Debug Output
N/A
Panic Output
N/A
Expected Behavior
Support for the following arguments related to Azurerm Express Route Circuit Peering (Microsoft Peering):
-PeerAddressType
-MicrosoftConfigCustomerAsn
-MicrosoftConfigRoutingRegistryName
https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-arm#next-steps
Actual Behavior
I don't see documentation or support for the following Azurerm Express Route Circuit Peering (Microsoft Peering) arguments:
-PeerAddressType
-MicrosoftConfigCustomerAsn
-MicrosoftConfigRoutingRegistryName
Steps to Reproduce
N/A
Important Factoids
N/A
References
Below is a powershell script with PeerAddressType, MicrosoftConfigCustomerAsn, and MicrosoftConfigRoutingRegistryName arguments:
Add-AzureRmExpressRouteCircuitPeeringConfig
-Name "MicrosoftPeering"
-ExpressRouteCircuit $ckt
-PeeringType MicrosoftPeering
-PeerASN 100
-PeerAddressType IPv4
-PrimaryPeerAddressPrefix "123.0.0.0/30"
-SecondaryPeerAddressPrefix "123.0.0.4/30"
-VlanId 300
-MicrosoftConfigAdvertisedPublicPrefixes "123.1.0.0/24"
-MicrosoftConfigCustomerAsn 23
-MicrosoftConfigRoutingRegistryName "ARIN"
https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-arm#next-steps
The text was updated successfully, but these errors were encountered: