[Bug]: aws_fsx_openzfs_volume always detects tags_all as being changed

[zampettim]

Terraform Core Version

1.9.0

AWS Provider Version

v5.56.1

Affected Resource(s)

aws_fsx_openzfs_volume

Expected Behavior

Running terraform plan for a manifest with the aws_fsx_openzfs_volume resource where nothing changes should result in no planned updates.

Actual Behavior

The aws_fsx_openzfs_volume resource is always seeing the tags_all parameters as being changed, even though the default_tags on the provider and the data in the AWS resource have not changed.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

provider "aws" {
  region = "us-east-1"
  alias  = "us-east-1"

  profile = "XXXX"

  # Make sure we are working on the right account
  allowed_account_ids = ["XXXXXXX"]

  default_tags {
    tags = {
      TerraformManaged = "YES"
      Environment      = "Development"
    }
  }
}

Steps to Reproduce

Create a manifest that creates the aws_fsx_openzfs_volume resource
Run terraform apply to create the resources
Run terraform plan again, and see that the tags_all is determined to need to be updated.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[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.

[justinretzolk]

Hey @zampettim 👋 Thank you for taking the time to raise this! Can you supply a sample Terraform configuration that can be used to reproduce the issue?

[ewbankkit]

Relates #37346.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. 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.

[github-actions]

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