Allow specification of names and tags for secondary CIDR blocks.

[jhancock93]

Is your request related to a new offering from AWS?

No

Is your request related to a problem? Please describe.

When secondary CIDR blocks are specified within the same availability zone, the Name tag of the subnets created for the primary and secondary CIDR blocks are identical, making them difficult to distinguish.

Describe the solution you'd like.

Ideally, the public_subnets, database_subnets, private_subnets, etc. would accept a map or list of objects instead of a list of strings so that additional name suffixes or prefixes or tags might be supplied to allow the multiple subnets to be distinguished. Since this would be a breaking change, it would probably require introducing new optional variables.

Describe alternatives you've considered.

None.

Additional context

In our case, we have a small secondary CIDR block that supports AWS DIrectConnect and we need an easy way to distinguish between the subnets.

[antonbabenko]

Thanks for opening this issue.

There are several similar already #403 #535, so I am going to close this one.

The common solution is to use maps instead of lists as you say.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.