Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data.tls_certificate.tls.certificates is empty list of object on tls provide 3.4.0 #31497

Closed
kailashsridharan opened this issue Jul 22, 2022 · 3 comments

Comments

@kailashsridharan
Copy link

Terraform Version

1.1.4
TLS Provider 4.0.0

Terraform Configuration Files

...

Debug Output

"aws_iam_openid_connect_provider" "openid_connect":
 thumbprint_list = [data.tls_certificate.tls.certificates[0].sha1_fingerprint]
data.tls_certificate.tls.certificates is empty list of object

Expected Behavior

The above error should not be seen, openid_connect should be successful

Actual Behavior

Error: Invalid index
data.tls_certificate.tls.certificates is empty list of object

Steps to Reproduce

data "tls_certificate" "tls" {
  url = aws_eks_cluster.this.identity[0].oidc[0].issuer
}

resource "aws_iam_openid_connect_provider" "openid_connect" {
  client_id_list  = ["sts.amazonaws.com"]
  thumbprint_list = [data.tls_certificate.tls.certificates[0].sha1_fingerprint]
  url             = aws_eks_cluster.this.identity[0].oidc[0].issuer
}

Additional Context

References

@kailashsridharan kailashsridharan added bug new new issue not yet triaged labels Jul 22, 2022
@kailashsridharan
Copy link
Author

Workaround is to set TLS provider to 3.4.0

@apparentlymart
Copy link
Contributor

Hi @kailashsridharan,

It seems like you're talking about a behavior of the hashicorp/tls provider, in which case I suggest to open an issue in the provider's own repository.

Since the current release of the provider is v4.0.0 it seems like the provider team have just made a major release which may contain intentional breaking changes. Therefore what you described might be the intended behavior and I would suggest reviewing the provider's changelog before you open an issue to confirm and to see if there are some migration steps you can follow to avoid the error.

Since the behavior you are describing isn't implemented in this repository, I'm going to close this issue. We use issues in this repository only to represents bugs and feature requests in Terraform CLI and Terraform Core, and not for individual providers that are developed and distributed separately. Thanks!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants