Conditionalize creation of Internet Gateway depending on whether public subnets are specified #1283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Internet Gateways are currently auto created even if no public subnets are configured.
For some customers with very strict security rules this causes compliance tests to fail.
This PR conditionalizes the creation of the Internet Gateway by checking if public subnets are specified. Only in this case the Internet Gateway is needed.
By conditionalizing the creation of the IGW the following breaking changes are introduced
internetGateway
output of the VPC module changes to being optional. Users that use the output will need to add a null/undefined check when using it. This breaking change should only affect users with advanced VPC setups that manually use the output of the IGWThis fixes #947