r/aws_codebuild_fleet: Allow base_capacity of 0 🤖🤖🤖

[Samuel-Harris]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

No.

Description

aws_codebuild_fleet rejected base_capacity = 0 in schema validation (validation.IntAtLeast(1)) even though AWS CloudFormation documents BaseCapacity with a minimum of 0. That blocked Terraform-managing a reserved fleet with no warm hosts.

This PR changes the validator to IntAtLeast(0), documents the minimum, and extends TestAccCodeBuildFleet_baseCapacity to create with 0 then update to 1.

AI usage: An LLM agent drafted the issue, schema/test/docs change, and this PR. I reviewed the diff and own the submission.

Relations

Closes #49911

References

• AWS::CodeBuild::Fleet BaseCapacity — Minimum: 0
• Registry docs previously omitted the floor

Output from Acceptance Testing

Acceptance tests were not run locally (no Go toolchain on this machine; also creates a real CodeBuild reserved fleet). Please run:

% make testacc TESTS=TestAccCodeBuildFleet_baseCapacity PKG=codebuild

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