Terraform AWS Provider doesn't provide a metadata for grouping and we try to determine the group from the second word in the snake case representation of the resource, i.e. aws_ec2_instance would be in ec2 as group.
However, there are legacy resources who don't conform this format. For example, there bunch of aws_default_<some resource> resources (like aws_default_vpc) that are just there to represent the default instance of said resource but are put under default group.
We need a smarter way of doing this classification and allow manual input in a nice way. The interface could possibly come from Terrajet.
Terraform AWS Provider doesn't provide a metadata for grouping and we try to determine the group from the second word in the snake case representation of the resource, i.e.
aws_ec2_instance
would be inec2
as group.However, there are legacy resources who don't conform this format. For example, there bunch of
aws_default_<some resource>
resources (likeaws_default_vpc
) that are just there to represent the default instance of said resource but are put underdefault
group.We need a smarter way of doing this classification and allow manual input in a nice way. The interface could possibly come from Terrajet.