Add data source for transit gateway's Direct Connect gateway attachment

[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

When a Direct Connect gateway is associated with a transit gateway a transit gateway attachment with resource type direct-connect-gateway is created.
We need a new data source to be able to obtain the ID of this attachment.
See this comment.

Related:

• Allow aws_dx_gateway_association and aws_dx_private_virtual_interface to reference Transit Gateway #8490
• r/aws_dx_gateway_association: Update for transit gateway support plus the second half (cross-account proposal acceptance) of support for Gateway Association Proposals #8528

Possible syntax:

data "aws_ec2_transit_gateway_dx_gateway_attachment" "example" {
  transit_gateway_id = "${aws_ec2_transit_gateway.example.id}"
  dx_gateway_id      = "${aws_dx_gateway.example.id}"
}

[bflad]

The new aws_ec2_transit_gateway_dx_gateway_attachment data source has been merged and will be released shortly with version 2.14.0 of the Terraform AWS Provider. Thanks, @ewbankkit!

[bflad]

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

[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!