Block type tags issue - Error: Unsupported block type

[berry2012]

Blocks of type "tags" are not expected here. Did you mean to define argument
"tags"? If so, use the equals sign to assign it a value.

resource "aws_s3_bucket" "code" {
  bucket        = "${var.domain_name}-${random_id.wp_code_bucket.dec}"
  acl           = "private"
  force_destroy = true

  tags {
    Name = "code bucket"
  }
}

terraform --version
Terraform v0.12.2
+ provider.aws v2.15.0
+ provider.random v2.1.2

[apparentlymart]

Hi @berry2012,

tags is an argument of aws_s3_bucket, rather than a nested object related to it, so you should use = to represent the fact that you are assigning a map value to that argument, rather than creating a nested object of type tags:

  tags = {
    Name = "code bucket"
  }

While the syntax difference between these two is subtle, the meaning is quite different: tags can accept any expression as long as its result is a map, and in this case we just happen to be using a literal map expression that uses the same delimiters as a nested block uses. The distinction is more apparent when tags is assigned from a more dynamic expression:

  tags = merge(local.default_tags, local.s3_tags, {
    Name = "code bucket"
  })

If you saw this error after upgrading an existing configuration from Terraform 0.11, I'd suggest reviewing the upgrade guide, which includes a tool to automatically fix this and several other quirks caused by the incomplete validation in Terraform 0.11's language implementation.

If you're writing this configuration in Terraform 0.12 for the first time and saw this incorrect tags declaration in some documentation, it'd be a great help if you could file an issue (probably in the AWS provider repository, if this was in the AWS provider documentation) so that we can get that documentation fixed to show the correct usage.

[hashibot]

Hello! 🤖

We use GitHub issues for tracking bugs and enhancements rather than for questions. While we can sometimes help with certain simple problems here, it's better to use the community forum where there are more people ready to help. The GitHub issues here are monitored only by our few core maintainers.

Since this issue doesn't represent a specific bug or feature request, I'm going to close it. Please do feel free to ask your question in the community forum. Thanks!

[ghost]

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.