TF plans show changes to db option groups when there are no changes

[rk7373]

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

Terraform v0.13

• provider registry.terraform.io/hashicorp/aws v3.63.0

Affected Resource(s)

• aws_db_option_group

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

sample config

resource "aws_db_option_group" "foo" {
  name = "foo"

  option_group_description = "Terraform Option Group"
  engine_name              = "oracle-se2"
  major_engine_version     = "12.1"

  option {
    option_name = "S3_INTEGRATION"
    version     = "1.0"
  }
}

Expected Behavior

Infrastructure matches the TF plan so no differences should be shown in the tf plan for the RDS option group

Actual Behavior

TF plan shows the RDS option group has changes and will be updated in place

# aws_db_option_group.foo will be updated in-place
 ~ resource "aws_db_option_group" "foo" {
 ...
  - option {
     - db_security_group_memberships  = [] -> null
     - option_name                    = "S3_INTEGRATION" -> null
     - port                           = 0 -> null
     - version                        = "1.0" -> null
     - vpc_security_group_memberships = [] -> null
  }
  + option {
    + db_security_group_memberships  = []
    + option_name                    = "S3_INTEGRATION"
    + version                        = "1.0"
    + vpc_security_group_memberships = []
  }

Steps to Reproduce

1. terraform plan

[mrg2k8]

I had the same issue and fixed it by updating to Terraform v1.0.11 and provider registry.terraform.io/hashicorp/aws v3.54.0.

[rk7373]

Thank you for the feedback, this is good to know. We have updating to Terraform v1 on the roadmap

[r2c2]

I still face the issue with terraform v1.011 and aws provider v3.65.0

[rk7373]

I still face the same issue using tf1.0.11 and the following aws provider versions

• v3.54.0
• v3.65.0
• v3.68.0

[ChastinaLi]

facing this with aws provider v5.10.0 and terraform v1.3.0

[github-actions]

This functionality has been released in v5.18.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.