aws_glue_catalog_database with target_database but without location_uri stays permanently out of sync

[chrisbulgaria]

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

Terraform CLI and Terraform AWS Provider Version

3.42

Affected Resource(s)

• aws_glue_catalog_database

Terraform Configuration Files

resource "aws_glue_catalog_database" "ext_db" {
    name  = "${var.db_name}_db"
    target_database {
      catalog_id    = var.ext_acct
      database_name = var.ext_db
    }
}

Debug Output

Plan:

~ resource "aws_glue_catalog_database" "ext_db" {
id = "xxxxx"
- location_uri = "yyyyyy" -> null
name = "zzzz"
# (3 unchanged attributes hidden)
# (1 unchanged block hidden)
}

Expected Behavior

No change detected

Actual Behavior

It seems to pull in the location_uri from the target_db (which is not in the resource def) and then stays permanently out of sync.

target_database support was recently added:
#15296

[DrFaust92]

seems like location_uri needs to be computed here. as a workaround you can add the following block meanwhile:

lifecycle {
  ignore_changes = [location_uri]
}

[github-actions]

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.