ConfigDocument JSON always triggers change with whitespace

[hashibot]

This issue was originally opened by @artburkart as hashicorp/terraform#6289. It was migrated here as part of the provider split. The original body of the issue is below.

---

Hi there,

Terraform Version

$ terraform version
Terraform v0.6.14

Affected Resource(s)

Please list the resources as a list, for example:

• aws_elastic_beanstalk_environment

Terraform Configuration Files

Doesn't trigger change

  setting = {
    namespace = "aws:elasticbeanstalk:healthreporting:system"
    name = "ConfigDocument"
    value = <<EOF
{"Version":1,"CloudWatchMetrics":{"Instance":{"ApplicationRequestsTotal":60},"Environment":{"ApplicationRequests5xx":60,"ApplicationRequests4xx":60,"ApplicationRequests2xx":60}}}EOF
  }

Triggers change

  setting = {
    namespace = "aws:elasticbeanstalk:healthreporting:system"
    name = "ConfigDocument"
    value = <<EOF
    {
    "CloudWatchMetrics": {
      "Environment": {
        "ApplicationRequests2xx": 60,
        "ApplicationRequests5xx": 60,
        "ApplicationRequests4xx": 60
      },
      "Instance": {
        "ApplicationRequestsTotal": 60
      }
    },
    "Version": 1
    }
    EOF
  }

Expected Behavior

terraform plan shouldn't expect a change with this config setting

Actual Behavior

Every time I run terraform plan, a change is expected, except when I copy and paste the output of the terraform plan and use it in the JSON keys in the exact same order without any whitespace.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
2. terraform plan

Important Factoids

Nothing special

References

Similar to 6257, but not the same.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!