Ensure correct VIF type during import of Direct Connect Virtual Interfaces

[ewbankkit]

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

The aws_dx_private_virtual_interface, aws_dx_public_virtual_interface and aws_dx_transit_virtual_interface all support resource import via terraform import. As the same underlying AWS Direct Connect API call is used in all cases, it is possible to import e.g. a transit VIF as a private VIF. The API returns a VirtualInterfaceType property so we should check that this has the correct value before allowing the import to succeed.

Related:

• aws_dx_private_virtual_interface: 8500 MTU #8841

[ewbankkit]

Verifying correct VIF type while importing aws_dx_transit_virtual_interface, aws_dx_hosted_transit_virtual_interface and aws_dx_hosted_transit_virtual_interface_accepter implemented in #8522 and #8523 respectively.

[bflad]

This has been implemented for aws_dx_private_virtual_interface and aws_dx_public_virtual_interface via #9572 and will release with version 2.40.0 of the Terraform AWS Provider, later this week.

[ghost]

This has been released in version 2.40.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

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. Thanks!