r/aws_emrcontainers_job_template: Add parameter_configuration support

[mark-liu]

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.

Description

The AWS SDK exposes ParameterConfiguration on JobTemplateData but the Terraform resource doesn't model it. Without this field, users can't define template parameters (referenced as ${ParameterName} placeholders) and StartJobRun with --job-template-parameters fails with "Parameter not defined".

This adds parameter_configuration as an optional TypeSet block under job_template_data with three attributes:

• name — the parameter name (map key in the API)
• type — STRING or NUMBER (validated via enum.Validate)
• default_value — optional default

Used TypeSet of blocks with a name key attribute since SDKv2 doesn't support maps of blocks natively. Same pattern as securityhub/configuration_policy.go.

Relations

Closes #46502

References

• AWS SDK: JobTemplateData.ParameterConfiguration — map[string]TemplateParameterConfiguration (already in sdk v1.40.15)
• AWS docs: https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/job-templates.html

Output from Acceptance Testing

% make testacc TESTS=TestAccEMRContainersJobTemplate_parameterConfiguration PKG=emrcontainers

...

[github-actions]

Welcome @mark-liu 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider repository. Thank you very much for taking the time to do so, and welcome to the community! 🎉

---

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]

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

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