r/aws_redshiftserverless_workgroup: allow enable_large_strings_opt_in config parameter

[shashankvarma499]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #49939

Amazon Redshift Serverless now returns enable_large_strings_opt_in from GetWorkgroup (introduced with Redshift Patch 205 for larger individual strings in the SUPER data type). Because the provider rejects this key in config_parameter.parameter_key validation, a workgroup whose API response includes it produces a perpetual diff, and every apply that touches the workgroup fails with:

ValidationException: You didn't specify any changes to the configuration parameters.

The AWS API accepts the key (verified via the CLI in the linked issue), so the fix is to add it to the allowed parameter_key values. This mirrors the existing handling of the require_ssl / use_fips_ssl parameters that AWS surfaces automatically.

Output from acceptance testing:

% make testacc TESTS=TestAccRedshiftServerlessWorkgroup_configParameters PKG=redshiftserverless
... (requires AWS credentials; not run in this environment)

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