[Bug]: aws_cloudwatch_log_group invalid value for skip_destroy

[grahamhar]

Terraform Core Version

1.3.9,1.4.2

AWS Provider Version

4.54.0,4.60.0

Affected Resource(s)

aws_cloudwatch_log_group

Expected Behavior

The plan/apply should have completed without error

Actual Behavior

The apply errored following introduction of the attribute skip_destroy

Relevant Error/Panic Output Snippet

│ aws_cloudwatch_log_group.log_group
    │ to include new values learned so far during apply, provider
    │ "registry.terraform.io/hashicorp/aws" produced an invalid new value for
    │ .skip_destroy: was cty.False, but now null.
    │
    │ This is a bug in the provider, which should be reported in the provider's
    │ own issue tracker.

Terraform Configuration Files

resource "aws_cloudwatch_log_group" "yada" {
name = "Yada"
skip_destroy = var.skip
}

variable "skip" {
type = bool
default = false
}

Steps to Reproduce

We could not reproduce when trying the same configuration on a different stack.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

Yes

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

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.

[SizZiKe]

@justinretzolk what's blocking this from being released?

[github-actions]

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