provider/aws: Support multiple subnets in Network ACL #1931
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.
Ref #1717
The AWS API allows Network ACLs to be applied to multiple subnets, but Terraform is currently limited to 1-to-1. With this PR we introduce
subnet_ids
and deprecatesubnet_id
, so you can a single ACL to multiple subnets.Subnets in a VPC must be assigned an ACL, so, if we remove a subnet from this ACL, that subnet gets associated to the Default ACL. This needs to be documented because it could have weird behavior.
Usage:
State generated: (things omitted)
Needs:
sort.Strings
here, but the sorting is still not correct. This may be because I didn't sort them in the config(?). Not sure what to do about that.. ~~ fixed by making it aTypeSet
fromTypeList