Category name for aws_ec2_transit_gateway_route_table_association resource has been changed from 4.10.0v onwards

[Shivani2203]

Description

In the terraform documentation of 'aws_ec2_transit_gateway_route_table_association' resource, previously category of this resource was "EC2", but from 4.10.0v onwards Terraform categorizes this resource under "Transit Gateway".

Wanted to know the reason for the change in category of this resource from EC2 to Transit Gateway

References

Terraform Provider version 4.9.0 https://registry.terraform.io/providers/hashicorp/aws/4.9.0/docs/resources/ec2_transit_gateway_route_table_association

Terraform Provider version 4.10.0 https://registry.terraform.io/providers/hashicorp/aws/4.10.0/docs/resources/ec2_transit_gateway_route_table_association

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hey @Shivani2203 👋 Thank you for taking the time to raise this! This happened with #24158 as part of a larger effort to split up the EC2 resources into subcategories to make navigating the EC2 section of the documentation a bit more manageable (since there are so many EC2-related resources).

[Shivani2203]

Since the question is answered , I am closing the issue.

[github-actions[bot]]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.