Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global Tags for AWS provider #5435

Closed
paultyng opened this issue Mar 2, 2016 · 9 comments
Closed

Global Tags for AWS provider #5435

paultyng opened this issue Mar 2, 2016 · 9 comments

Comments

@paultyng
Copy link
Contributor

paultyng commented Mar 2, 2016

I apologize if this has already been written up in an issue, I searched but didn't find anything.

We use cost allocation tags in our AWS account when doing our reports for accounting purposes. When building out a Terraform environment, the vast majority of resources should all be tagged very similarly (owner, environment, app) and then we set / override tags in each specific resource on a case by case basis (specific service something is running, ie. consul, etc). It would be nice not to have to redundantly specify these tags on every resource that supports them (and also keep up to date on when tag support is added to a resource and have to go back and add those). It would also be nice for tags to flow down through modules using the same provider.

I can see a couple possible solutions:

  • Global tags set on the aws provider
  • Some ability to merge a map of tags in to resources instead of manually writing out each tag k/v pair, but the issue with this is child module support.
@gusmat
Copy link
Contributor

gusmat commented Mar 2, 2016

+1

@joshuaspence
Copy link
Contributor

+1

@paultyng
Copy link
Contributor Author

This is probably a same / duplicate of #2283.

Some other related issues: #3531, #5356, #4380, #1296

@serialseb
Copy link

Yes indeed, same as #2283

@apparentlymart
Copy link
Member

I'm going to close this in favor of #2283, to consolidate the discussion. Thanks, @paultyng!

@huyanhvn
Copy link
Contributor

+1

@farvour
Copy link

farvour commented Aug 30, 2017

+1

1 similar comment
@spacefuntus
Copy link

+1

@ghost
Copy link

ghost commented Jul 25, 2019

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.

@hashicorp hashicorp locked and limited conversation to collaborators Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants