Adds placement_group_config block to aws_emr_cluster resource

[gcardonag]

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

Output from acceptance testing:

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

For more background, this is related to the ability to deploy EMR master nodes in an EC2 Placement Group: https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-ha-placementgroup.html

[github-actions]

Welcome @gcardonag 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

[bryantbiggs]

ah nice - opened an issue for this #29665 but nice to see theres already a PR!

[gcardonag]

I was tinkering with syncing my fork to address the merge conflicts, which closed this PR. I'll open a new one shortly to replace this one

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