Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

AWS Groupping (VPC/Subnets/Region) #6

Open
xescugc opened this issue Jul 15, 2020 · 1 comment · May be fixed by #37
Open

AWS Groupping (VPC/Subnets/Region) #6

xescugc opened this issue Jul 15, 2020 · 1 comment · May be fixed by #37
Assignees

Comments

@xescugc
Copy link
Member

xescugc commented Jul 15, 2020

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.

@xescugc xescugc self-assigned this Jul 15, 2020
@xescugc xescugc changed the title Groupping (VPC/Subnets) Groupping (VPC/Subnets/Region) Jul 17, 2020
@xescugc xescugc changed the title Groupping (VPC/Subnets/Region) AWS Groupping (VPC/Subnets/Region) Jul 17, 2020
@xlr-8
Copy link

xlr-8 commented Jul 21, 2020

Regarding the grouping mechanism, there are several more:

  1. Region
  2. VPC
  3. Security group (when there are more than 1 instance for example)
  4. Subnets
  5. 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.

@xescugc xescugc linked a pull request Aug 7, 2020 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants