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

Tags repeatedly marked as not being set correctly for aws_db_instance #9821

Closed
davedash opened this issue Nov 2, 2016 · 3 comments
Closed

Comments

@davedash
Copy link
Contributor

davedash commented Nov 2, 2016

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.

@catsby
Copy link
Contributor

catsby commented Nov 3, 2016

Hey @davedash can you try running a refresh or plan with debugging enabled?

$ TF_LOG=1 terraform refresh

I'm looking for logs involving the tags, something like either:

Error building ARN for DB Instance, not setting Tags for DB

or

[DEBUG] Error retrieving tags for ARN: <arn>

@catsby catsby added the waiting-response An issue/pull request is waiting for a response from the community label Nov 3, 2016
@davedash
Copy link
Contributor Author

Thanks. This uncovered what I think the culprit is.

User: * is not authorized to perform: rds:ListTagsForResource on resource: *

This error is worth surfacing, IMO.

@ghost
Copy link

ghost commented Apr 10, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
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

4 participants