Tags repeatedly marked as not being set correctly for aws_db_instance

[hashibot]

This issue was originally opened by @davedash as hashicorp/terraform#9821. It was migrated here as part of the provider split. The original body of the issue is below.

---

In Terraform 0.7.8 (and prior):

terraform plan gives me:

~ module.dev.aws_db_instance.db
    tags.%:      "0" => "3"
    tags.Name:   "" => "dbdev"
    tags.dbrole: "" => "master"
    tags.env:    "" => "dev"

My tf file looks like:

resource "aws_db_instance" "db" {
    ...
    engine               = "postgres"
    engine_version       = "9.5.2"
    instance_class       = "db.m3.medium"
    db_subnet_group_name = "${aws_db_subnet_group.db.name}"
    storage_encrypted    = true
    parameter_group_name = "${var.parameter_group}"  # summit custom
    allow_major_version_upgrade = true

    tags {
      Name = "${var.env}"
      dbrole = "master"
      env = "${var.env}"
    }
...

After an apply, the tags are set. Re-running plan gives me the same output, so I'm always in a dirty state.

This is the case for all of my rds instances.

[bflad]

Courtesy of #4943, the aws_db_instance resource will properly return any ListTagsForResource error (our normal behavior for other parts of Terraform) instead of just a debug log and perpetual difference in terraform plan. It will be released in version 1.25.0 of the AWS provider, likely middle of next week.

[bflad]

This has been released in version 1.25.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!