Consistent ID across multiple planning

[caruccio]

Terraform Version

terraform -v
Terraform v0.13.2
+ provider registry.terraform.io/hashicorp/tls v2.2.0

Affected Resource(s)

Please list the resources as a list, for example:

• tls_certificate

Terraform Configuration Files

data "tls_certificate" "oidc_idp" {
  url = "https://oidc.eks.sa-east-1.amazonaws.com/id/<REDACTED>"
}

Expected Behavior

Consistent id across consecutive plans.

Actual Behavior

Resource id changes every plan even if certificates are the same.

...
      ~ id           = "2020-09-14 19:34:14.498463939 +0000 UTC" -> "2020-09-14 19:34:14.722109742 +0000 UTC"
...

Steps to Reproduce

1. terraform plan .
2. terraform apply .
3. terraform plan .

Important Factoids

Obviously, this is the behavior given by this line.
Is this intentional? Could it be something stable, like the certificate's serial number or sha1 fingerprint?

[Fuuzetsu]

The problem is made worse by the fact that the usual lifecycle { ignore_changes = [id] } approach one might want to take does not work:

Error: Unsupported lifecycle block

  on ../modules/main_vpc/eks.tf line 338, in data "tls_certificate" "oidc":
 338:   lifecycle {

Data resources do not have lifecycle settings, so a lifecycle block is not
allowed.

[xenji]

So, would the sha1_fingerprint be a good ID? It would have the positive side-effect, that it would make a change in this property very visible.

[amirba-mistral]

Any new info, does somebody found solutions to this problem?

[Z3R6]

Any updates?

[amirba-mistral]

Any updates?

I solve this problem with an update of Terraform to version "0.14.2".

[caruccio]

@amirba-mistral AFAIU this is the line that sets this id: https://github.com/hashicorp/terraform-provider-tls/blob/v3.0.0/internal/provider/data_source_tls_certificate.go#L109

What is the provider version you are using?

[Z3R6]

Any updates?

I solve this problem with an update of Terraform to version "0.14.2".

I also solved this problem with update Terraform to version "0.14.2".
Thanks!

[github-actions]

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.