You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the logic for VPCs, Subnets and Regions. The idea is to have a Grouping between resources that belong to the same VPC, Subnet and/or Region.
On AWS reading the TFState/HCL we are able to know if some resource belong to those:
VPC: vpc_id and vpc_security_group_ids.
Subnets: TBD
Region: TBD
The idea would be to add a Groups on the provider.Provider that does the same as ResourceInOut that returns which groups the resource belongs to and then from that extend to different Providers bit by bit.
The text was updated successfully, but these errors were encountered:
Regarding the grouping mechanism, there are several more:
Region
VPC
Security group (when there are more than 1 instance for example)
Subnets
Availability Zone (nice addition to the region one)
I'm not sure of the order of priority though, region/VPC seem fairly straight forward and good to start with.
Perhaps security groups & subnets afterwards, while leaving the AZ for the last.
Add the logic for VPCs, Subnets and Regions. The idea is to have a Grouping between resources that belong to the same VPC, Subnet and/or Region.
On
AWS
reading the TFState/HCL we are able to know if some resource belong to those:vpc_id
andvpc_security_group_ids
.The idea would be to add a
Groups
on theprovider.Provider
that does the same asResourceInOut
that returns which groups the resource belongs to and then from that extend to different Providers bit by bit.The text was updated successfully, but these errors were encountered: