[TF 0.13] Data Resource Detects Diff in the absence of code changes after TF upgrade

[ranimufid]

Terraform Version

v0.13.0

Terraform Configuration Files

data "aws_acm_certificate" "mydomain" {
  count    = var.public_dns ? 1 : 0
  domain   = "${terraform.workspace == "production" ? "*.cdn.mydomain.net" : "*.shared-${terraform.workspace}.mydomain.net"}"
  statuses = ["ISSUED"]
}

resource "kubernetes_ingress" "public" {
  count = var.public_dns ? 1 : 0
  metadata {
    name      = "${var.kubernetes_deployment_name}-public"
    namespace = var.namespace
    labels = {
      env      = terraform.workspace
      app_name = "${var.kubernetes_deployment_name}-${terraform.workspace}"
    }
    annotations = {
      "kubernetes.io/ingress.class"                            = "alb"
      "alb.ingress.kubernetes.io/certificate-arn"              = data.aws_acm_certificate.audibene[0].arn     
    }
  }

Expected Behavior

Considering that I have made no changes to the resource referenced by the data.aws_acm_certificate, I would have expected to see

No changes. Infrastructure is up-to-date.

Actual Behavior

 <= data "aws_acm_certificate" "audibene"  {
        arn         = "arn:aws:acm:eu-central-1:123456789:certificate/12nkr23-123df-123sd-1adf-123f212d"
        domain      = "*.shared-testing.mydomain.net"
      ~ id          = "2020-08-17 10:33:04.062011 +0000 UTC" -> "2020-08-17 10:33:08.830861 +0000 UTC"
        most_recent = false
        statuses    = [
            "ISSUED",
        ]
        tags        = {}
    }

Steps to Reproduce

• Terraform plan

Additional Context

Terraform didn't detect a diff when using the same TF code with terraform v0.12.29

[remilapeyre]

Hi @ranimufid, this is a duplicate of #25858 and hashicorp/terraform-provider-aws#14579.

[ranimufid]

Thanks for the info @remilapeyre. Will proceed to close this issue in favour of the already open ones you shared!

[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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.