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

default_tags and resource tags should be allowed to be identical #19760

Closed
jrobison-sb opened this issue Jun 10, 2021 · 2 comments
Closed

default_tags and resource tags should be allowed to be identical #19760

jrobison-sb opened this issue Jun 10, 2021 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. provider Pertains to the provider itself, rather than any interaction with AWS. service/sns Issues and PRs that pertain to the sns service.

Comments

@jrobison-sb
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

If a resource has a set of tags which are identical to the set of default_tags, that should be allowed and not cause an error. Currently it causes terraform plan to produce an error saying Error: "tags" are identical to those in the "default_tags" configuration block of the provider: please de-duplicate and try again.

It's possible to merge({a="b"}, {a="b"}) and get the expected output of {"a" = "b"}, so default_tags and a resource's tags attribute should behave similarly.

New or Affected Resource(s)

  • default_tags, and every resource

Potential Terraform Configuration

provider "aws" {
  default_tags {
    tags = {
      Environment = "production"
    }
  }
}

resource "aws_sns_topic" "foo" {
  name  = "whatever"
  tags = {
    Environment = "production"
  }
}
@jrobison-sb jrobison-sb added the enhancement Requests to existing resources that expand the functionality or scope. label Jun 10, 2021
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/sns Issues and PRs that pertain to the sns service. labels Jun 10, 2021
@anGie44 anGie44 added provider Pertains to the provider itself, rather than any interaction with AWS. and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 10, 2021
@anGie44
Copy link
Contributor

anGie44 commented Jun 10, 2021

Hi @jrobison-sb , thank you raising this issue. It's definitely something we're exploring and there is an open issue #19204 that tracks the issue users are facing as well provides more context behind the design choice. I'm going to close this as a duplicate, but please refer to #19204 for future updates!

@anGie44 anGie44 closed this as completed Jun 10, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. provider Pertains to the provider itself, rather than any interaction with AWS. service/sns Issues and PRs that pertain to the sns service.
Projects
None yet
Development

No branches or pull requests

2 participants