Subsequent plan/apply forces global cluster recreation when source cluster's storage_encrypted=true

[marinsalinas]

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

Affected Resource(s)

• aws_rds_global_cluster

Terraform Configuration Files

data "aws_kms_alias" "this" {
  name  = "alias/rds"
}


# The source_db_cluster_identifier argument does not currently exist
resource "aws_rds_global_cluster" "global_cluster" {
  # ... other configuration ...
  source_db_cluster_identifier = aws_rds_cluster.example.id
}

resource "aws_rds_cluster" "example" {
  snapshot_identifier = aws_db_cluster_snapshot.example.id

  storage_encrypted = true
  kms_key_id              =  data.aws_kms_alias.this.target_key_arn

  lifecycle {
    ignore_changes = [global_cluster_identifier]
  }
}

Debug Output

Panic Output

Expected Behavior

Subsequent plans should show no changes.

Actual Behavior

The subsequent plan shows a diff on the storage_encrypted attribute since now this attribute is marked as optional, it should be computed as well.

/+ resource "aws_rds_global_cluster" "global_cluster" {
      ...
      - storage_encrypted            = true -> null # forces replacement
    }

Steps to Reproduce

1. terraform apply
2. terraform plan

Important Factoids

storage_encrypted should be Computed as well.
https://github.com/terraform-providers/terraform-provider-aws/blob/master/aws/resource_aws_rds_global_cluster.go#L99

[callaingit]

I had the same issue, needed to add a lifecycle to ignore changes on storage_encrypted as a work-around.

[bflad]

I'm working on similar fixes for other attributes in the RDS resources, so picking this up as part of those efforts.

[bflad]

The fix for this has been merged and will release with version 3.13.0 of the Terraform AWS Provider, likely later today. 👍

[ghost]

This has been released in version 3.13.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 for triage. 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!