[Bug]: aws_placement_group forces recreate without optional spread_level arg

[jonathanstockton]

Terraform Core Version

1.3.0

AWS Provider Version

4.31.0

Affected Resource(s)

aws_placement_group

Expected Behavior

When re-applying after initial creation, no changes should be made:

resource "aws_placement_group" "thing" {
  name     = "thing"
  strategy = "spread"
}

Actual Behavior

Resource is marked for recreation with changes in optional parameters:

resource "aws_placement_group" "proxy_placement" {
  ~ arn                = "xxxx" -> (known after apply)
  ~ id                 = "thing" -> (known after apply)
    name               = "thing"
  ~ partition_count    = 0 -> (known after apply)
  ~ placement_group_id = "pg-034752b34588fb238" -> (known after apply)
  - spread_level       = "rack" -> null # forces replacement
  - tags               = {} -> null
  ~ tags_all           = {} -> (known after apply)
    # (1 unchanged attribute hidden)
}

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

terraform {
  required_version = "= 1.3.0"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "4.31.0"
    }
  }
}

provider "aws" {
  region = "eu-west-1
}

resource "aws_placement_group" "thing" {
  name     = "thing"
  strategy = "spread"
}

Steps to Reproduce

Apply terraform containing "aws_placement_group" resources without optional "spread_level" parameter multiple times

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

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

[DoctorPolski]

Probably as a result of: #25615

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