bugfix: aws_ec2_placement_group spread level

[bennylu2]

Description

As mentioned in the bug that was reported, the new spread_level argument forced replacements. This was because the API returns rack as a default value when strategy is set to spread.

• Fixed up documentation
• Removed double-quotes to standardize

Relations

Closes #26958

Tests

make testacc TESTS='TestAccEC2PlacementGroup_spreadLevel' PKG=ec2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ec2/... -v -count 1 -parallel 20 -run='TestAccEC2PlacementGroup_spreadLevel'  -timeout 180m
=== RUN   TestAccEC2PlacementGroup_spreadLevel
=== PAUSE TestAccEC2PlacementGroup_spreadLevel
=== CONT  TestAccEC2PlacementGroup_spreadLevel
--- PASS: TestAccEC2PlacementGroup_spreadLevel (33.14s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ec2        50.558s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[bennylu2]

Is there a way to run/limit the linters locally to only files that have had changes? Something like pre-commit or being able to specify a path? I feel like I may be missing something unless everyone's supposed to lint the entire codebase each time

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccEC2PlacementGroup_' PKG=ec2 ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ec2/... -v -count 1 -parallel 2  -run=TestAccEC2PlacementGroup_ -timeout 180m
=== RUN   TestAccEC2PlacementGroup_basic
=== PAUSE TestAccEC2PlacementGroup_basic
=== RUN   TestAccEC2PlacementGroup_disappears
=== PAUSE TestAccEC2PlacementGroup_disappears
=== RUN   TestAccEC2PlacementGroup_tags
=== PAUSE TestAccEC2PlacementGroup_tags
=== RUN   TestAccEC2PlacementGroup_partitionCount
=== PAUSE TestAccEC2PlacementGroup_partitionCount
=== RUN   TestAccEC2PlacementGroup_defaultSpreadLevel
=== PAUSE TestAccEC2PlacementGroup_defaultSpreadLevel
=== RUN   TestAccEC2PlacementGroup_spreadLevel
=== PAUSE TestAccEC2PlacementGroup_spreadLevel
=== CONT  TestAccEC2PlacementGroup_basic
=== CONT  TestAccEC2PlacementGroup_partitionCount
--- PASS: TestAccEC2PlacementGroup_basic (24.74s)
=== CONT  TestAccEC2PlacementGroup_tags
--- PASS: TestAccEC2PlacementGroup_partitionCount (24.84s)
=== CONT  TestAccEC2PlacementGroup_disappears
--- PASS: TestAccEC2PlacementGroup_disappears (17.06s)
=== CONT  TestAccEC2PlacementGroup_spreadLevel
--- PASS: TestAccEC2PlacementGroup_spreadLevel (22.89s)
=== CONT  TestAccEC2PlacementGroup_defaultSpreadLevel
--- PASS: TestAccEC2PlacementGroup_tags (53.49s)
--- PASS: TestAccEC2PlacementGroup_defaultSpreadLevel (22.92s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ec2	97.809s

[ewbankkit]

@bennylu2 Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v4.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 pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.