Enable setting of 0 for sampling_rate

[Ken-Sumi1019]

Resource:aws_cloudfront_response_headers_policy.server_timing_headers_config

Description

Allow 0 for sampling_rate in server_timing_headers_config.

Relations

Closes #27721

References

Output from Acceptance Testing

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

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

[YakDriver]

LGTM 🎉

% make t T=TestAccCloudFrontResponseHeadersPolicy_ K=cloudfront
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/cloudfront/... -v -count 1 -parallel 20 -run='TestAccCloudFrontResponseHeadersPolicy_'  -timeout 180m
=== RUN   TestAccCloudFrontResponseHeadersPolicy_cors
=== PAUSE TestAccCloudFrontResponseHeadersPolicy_cors
=== RUN   TestAccCloudFrontResponseHeadersPolicy_customHeaders
=== PAUSE TestAccCloudFrontResponseHeadersPolicy_customHeaders
=== RUN   TestAccCloudFrontResponseHeadersPolicy_securityHeaders
=== PAUSE TestAccCloudFrontResponseHeadersPolicy_securityHeaders
=== RUN   TestAccCloudFrontResponseHeadersPolicy_serverTimingHeaders
=== PAUSE TestAccCloudFrontResponseHeadersPolicy_serverTimingHeaders
=== RUN   TestAccCloudFrontResponseHeadersPolicy_disappears
=== PAUSE TestAccCloudFrontResponseHeadersPolicy_disappears
=== CONT  TestAccCloudFrontResponseHeadersPolicy_cors
=== CONT  TestAccCloudFrontResponseHeadersPolicy_serverTimingHeaders
=== CONT  TestAccCloudFrontResponseHeadersPolicy_securityHeaders
=== CONT  TestAccCloudFrontResponseHeadersPolicy_customHeaders
=== CONT  TestAccCloudFrontResponseHeadersPolicy_disappears
--- PASS: TestAccCloudFrontResponseHeadersPolicy_disappears (14.67s)
--- PASS: TestAccCloudFrontResponseHeadersPolicy_customHeaders (18.71s)
--- PASS: TestAccCloudFrontResponseHeadersPolicy_securityHeaders (29.92s)
--- PASS: TestAccCloudFrontResponseHeadersPolicy_cors (30.55s)
--- PASS: TestAccCloudFrontResponseHeadersPolicy_serverTimingHeaders (49.48s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/cloudfront	51.331s

[github-actions]

This functionality has been released in v4.55.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.