resource/aws_placement_group: Remove hardcoded upper limit for partition_count

[revtron]

Description

This PR removes the hardcoded upper limit (7) for the partition_count argument in the aws_placement_group resource.

AWS has mutable service limits for partition count, so Terraform should defer validation to the AWS API instead of enforcing a static upper bound. This change replaces validation.IntBetween(0, 7) with validation.IntAtLeast(0).

Motivation and Context

Deferring this validation to AWS allows Terraform to remain compatible with future updates without requiring provider releases whenever limits change.

This aligns with HashiCorp’s principle of avoiding hardcoded API limits that can change on the AWS side.

Affected Resource(s)

• aws_placement_group

Changes Made

- ValidateFunc: validation.IntBetween(0, 7),
+ ValidateFunc: validation.IntAtLeast(0),

[github-actions]

Community Guidelines

This comment is added to every new Pull Request 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 Pull Request 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 Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[ChaosCypher]

PR already opened and under review here - #45042

In the future please check the issue for existing contributions so duplicate work isn't done.

[revtron]

PR already opened and under review here - #45042

In the future please check the issue for existing contributions so duplicate work isn't done.

Yes sure will look into ,this was my first contribution wasn't aware.

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