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

Add support ipv6 configuration in azurerm_express_route_circuit_peering #9235

Merged

Conversation

xuzhang3
Copy link
Contributor

AccTests Result:
image

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @xuzhang3 - overall this looks good and i've left some comments inline to address

website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
SecondaryPeerAddressPrefix: utils.String(v["secondary_peer_address_prefix"].(string)),
MicrosoftPeeringConfig: expandExpressRouteCircuitPeeringMicrosoftConfig(v["microsoft_peering_config"].([]interface{})),
}
routeFilterId := v["route_filter_id"].(string)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we add validation to check this is not set when incompatible types are used?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see a check for this anywhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still don't see a check to make sure route filter id is not set when type is microsoft in that link..

Copy link
Contributor Author

@xuzhang3 xuzhang3 Nov 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ipv6 is a little different with microsoft_peering_config, it is only supported by MicrosoftPeering. I add a check for ipv6 not route_filter_id, if peering type is not MicrosoftPeering and ipv6 is configured, an error message will raise up.
Check ipv6 configure:
https://github.com/xuzhang3/terraform-provider-azurerm/blob/f/expressroutecircuitpeering_enhance/azurerm/internal/services/network/express_route_circuit_peering_resource.go#L267

@xuzhang3 xuzhang3 requested a review from katbyte November 17, 2020 02:57
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @xuzhang3 - left some more comments inline

website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
SecondaryPeerAddressPrefix: utils.String(v["secondary_peer_address_prefix"].(string)),
MicrosoftPeeringConfig: expandExpressRouteCircuitPeeringMicrosoftConfig(v["microsoft_peering_config"].([]interface{})),
}
routeFilterId := v["route_filter_id"].(string)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see a check for this anywhere?

@xuzhang3 xuzhang3 requested a review from katbyte November 19, 2020 06:11
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @xuzhang3 - i still don't see a check to ensure route filter id is not set when the type is incorrect

SecondaryPeerAddressPrefix: utils.String(v["secondary_peer_address_prefix"].(string)),
MicrosoftPeeringConfig: expandExpressRouteCircuitPeeringMicrosoftConfig(v["microsoft_peering_config"].([]interface{})),
}
routeFilterId := v["route_filter_id"].(string)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still don't see a check to make sure route filter id is not set when type is microsoft in that link..

website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
website/docs/r/express_route_circuit_peering.html.markdown Outdated Show resolved Hide resolved
@xuzhang3 xuzhang3 requested a review from katbyte November 20, 2020 08:13
@tombuildsstuff tombuildsstuff added this to the v2.38.0 milestone Nov 20, 2020
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @xuzhang3 - LGTM 👍

@katbyte katbyte merged commit b7ebd5b into hashicorp:master Nov 23, 2020
katbyte added a commit that referenced this pull request Nov 23, 2020
@ghost
Copy link

ghost commented Nov 27, 2020

This has been released in version 2.38.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.38.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Dec 24, 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 as resolved and limited conversation to collaborators Dec 24, 2020
@xuzhang3 xuzhang3 deleted the f/expressroutecircuitpeering_enhance branch August 14, 2024 02:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants