Add/ignore cidr blocks

[colinh6]

what

• This PR will introduce logic to ignore certain CIDR ranges from either the requestor or acceptor VPC(s), without affecting the existing functionality.

why

• We add the CIDR range 100.64.0.0/16 to each of our EKS cluster VPCs to increase the maximum amount of assignable IP addresses when using the AWS VPC CNI.
• This causes issues when attempting to leverage this existing peering module, as the 100.64.0.0/16 routes will conflict in certain cases.
• One specific case is where we want to peer and route a single database or elasticsearch VPC to multiple different EKS cluster VPCs that all contain the 100.64.0.0/16 additional CIDR association

references

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/

[aknysh]

/test all

[aknysh]

@colinh6 thank you for the PR, looks good, but please fix these errors https://github.com/cloudposse/actions/actions/runs/3325626731/jobs/5498510030

[colinh6]

@colinh6 thank you for the PR, looks good, but please fix these errors https://github.com/cloudposse/actions/actions/runs/3325626731/jobs/5498510030

@aknysh Thank you for the review, I believe my latest commit should (hopefully) fix the errors. Could you please re-run the tests?

[aknysh]

please see comments

[colinh6]

please see comments

@aknysh I believe I have fixed that error. I have attempted to run terratest locally but am having a number of issues. Would you mind re-running the tests again for me? Much appreciated.

[ngoyal16]

/test all

[colinh6]

@aknysh I found some time and got the tests running locally, I have them passing now. Could you check again for me?

[aknysh]

/test all

[aknysh]

@colinh6 thanks again, please see the comments (please fix the error in terratest)

[aknysh]

/test all