Skip to content

Conversation

@Davidding4718
Copy link

Rollback Plan

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

Changes to Security Controls

No changes to security controls (access controls, encryption, logging) in this pull request.

Description

Updates the maximum length validation for pipeline_configuration_body from the previous limit to 2,621,440 bytes to align with AWS API specification.

The AWS OpenSearch Ingestion Service API allows pipeline configuration bodies up to 2,621,440 bytes (approximately 2.5MB), but the Terraform provider was enforcing a smaller limit. This change ensures users can deploy complex OpenSearch Ingestion pipelines with larger configuration bodies without encountering artificial validation errors from Terraform.

Relations

Relates #0000

References

AWS OpenSearch Ingestion API documentation specifies the PipelineConfigurationBody parameter has a maximum length of 2,621,440 bytes.

Output from Acceptance Testing

% make testacc TESTS=TestAccOSISPipeline PKG=osis

...

from the previous limit to 2,621,440 bytes to align with AWS API
specification.

Signed-off-by: Siqi Ding <[email protected]>
@Davidding4718 Davidding4718 requested a review from a team as a code owner October 30, 2025 19:21
@github-actions
Copy link
Contributor

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.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 30, 2025

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/osis Issues and PRs that pertain to the osis service. size/XS Managed by automation to categorize the size of a PR. labels Oct 30, 2025
@gdavison gdavison self-assigned this Nov 3, 2025
@github-actions github-actions bot added the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Nov 3, 2025
@justinretzolk justinretzolk added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Requests to existing resources that expand the functionality or scope. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. service/osis Issues and PRs that pertain to the osis service. size/XS Managed by automation to categorize the size of a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants