Unable to provide different tag names for different subnets

[ben5556]

I am creating a bunch of private subnets for Lambdas, Databricks components etc and I would like to tag them so as to be able to distinguish them when I look in AWS console

From what I can see in the current config, I cannot do this as the additional tags are not based on count/index ?

This is what I see on AWS console

example-public-ap-southeast-2a
example-private-ap-southeast-2c
example-private-ap-southeast-2b
example-db-ap-southeast-2b
example-db-ap-southeast-2c
example-private-ap-southeast-2a
example-db-ap-southeast-2b
example-private-ap-southeast-2b
example-db-ap-southeast-2a

How can I name them as below ?

example-public-ap-southeast-2a
example-databricks-private-ap-southeast-2c
example-lambda-private-ap-southeast-2b
example-databricks-db-ap-southeast-2b
example-databricks-db-ap-southeast-2c
example-lambda-private-ap-southeast-2a
example-generic-db-ap-southeast-2b
example-databricks-private-ap-southeast-2b
example-generic-db-ap-southeast-2a

[antonbabenko]

Currently, you can't do this in this module. You can try to use aws_ec2_tag resource to do what you want but it is not a very elegant solution.

I am going to close this issue because we already have #403 which is about a similar case (not entirely the same but the solution will cover this case, too).

[ben5556]

Thanks. May I know why something which is a common use case and also easy to implement was not included in this module ? Ability to tag each resource we are creating via this module is something basic yeah ?

[antonbabenko]

Primarily because this module started when it was not possible to implement such dynamic features.

We will have support for the features you described once we figure out the way to handle the migration path for the existing users (terraform does not have an easy way to specify the upgrade path as code, yet).

[ben5556]

Sorry, what migration/upgrade are you referring to ?

[antonbabenko]

hashicorp/terraform#19354
hashicorp/terraform#9048

[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.