TF recreates rules when it should not

[EugenKon]

Terraform and AWS Provider Version

Terraform v1.11.4
on darwin_arm64

Affected Resource(s) or Data Source(s)

• aws_s3_bucket_lifecycle_configuration

Expected Behavior

I added new rule, TF should just create it.

Actual Behavior

I added new rule, but TF recreates the existing one.

Relevant Error/Panic Output

  # module.private-cloud.aws_s3_bucket_lifecycle_configuration.iguides-s3 will be updated in-place
...
      ~ rule {
          ~ id     = "draft-queue" -> "delete-stitch-data/-1year"
            # (2 unchanged attributes hidden)

          ~ expiration {
              ~ days                         = 30 -> 365
                # (1 unchanged attribute hidden)
            }

          ~ filter {
              ~ prefix = "draft-queue/" -> "stitch-data/"
            }
        }
...
      + rule {
          + id     = "draft-queue"
          + status = "Enabled"
            # (1 unchanged attribute hidden)

          + expiration {
              + days                         = 30
              + expired_object_delete_marker = false
            }

          + filter {
              + prefix = "draft-queue/"
            }
        }

Sample Terraform Configuration

Click to expand configuration

resource "aws_s3_bucket_lifecycle_configuration" "iguides-s3" {
  bucket = aws_s3_bucket.iguides-s3.id

  # Delete stitch data after 1 year
  rule {
    id     = "delete-stitch-data/-1year"
    status = "Enabled"

    filter {
      prefix = "stitch-data/"
    }

    expiration {
      days                         = 365
      expired_object_delete_marker = false
    }
  }

  # Delete draft-queue/ after 30 days
  rule {
    id     = "draft-queue"
    status = "Enabled"

    filter {
      prefix = "draft-queue/"
    }

    expiration {
      days = 30
    }
  }
}

+  # Delete stitch data after 1 year
+  rule {
+    id     = "delete-stitch-data/-1year"
+    status = "Enabled"
+
+    filter {
+      prefix = "stitch-data/"
+    }
+
+    expiration {
+      days                         = 365
+      expired_object_delete_marker = false
+    }
+  }

Steps to Reproduce

1. Create lyfecycle with one rule
2. plan/apply
3. Add another rule before the first one
4. plan/apply
   TF will replace the first rule, though it should just add the new one.

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

Probably this belongs to:
#42202

There also array of some items and how TF works with them.

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[justinretzolk]

Hey @EugenKon 👋 Thanks for taking the time to submit this issue. It looks like this is a duplicate of #34645. We like to try to keep discussions consolidated, so we’re going to close this new issue in favor of that one.

[github-actions]

Warning

This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.