If Placement Group is not defined, then it recreates EMR everytime

[Jbhadviya]

Description

Terraform Version 1.6.4 Aws Provider Version 5.44.0

Terraform code ---

module "emr" {
  source = "terraform-aws-modules/emr/aws"

  name = "${lower(var.tenant_name)}-emr-cluster"

  release_label = var.emr_release
  applications  = var.emr_apps
  bootstrap_action = var.bootstrap_action
  configurations_json = jsonencode(var.config)

Terraform plan output ---

-/+ resource "aws_emr_cluster" "this" {
      ~ arn                               = "arn:aws:elasticmapreduce:us-west-2:XXX" -> (known after apply)
      ~ cluster_state                     = "WAITING" -> (known after apply)
      ~ configurations_json               = jsonencode([]) -> "null"
      ~ id                                = "XXXX" -> (known after apply)
      ~ keep_job_flow_alive_when_no_steps = true -> (known after apply)
      ~ log_uri                           = "s3n://XXX/hd-gdna-eng-c-emr-cluster/" -> "s3://XXX/hd-gdna-eng-c-emr-cluster/"
      ~ master_public_dns                 = "ip-XXX.us-west-2.compute.internal" -> (known after apply)
        name                              = "hd-gdna-eng-c-emr-cluster"
      - placement_group_config            = [] -> null

[Jbhadviya]

@bryantbiggs Can you pls check this.

[bryantbiggs]

I cannot check anything without a proper reproduction

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days