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

Seeing empty tls_certs error when trying to run examples/complete #2171

Closed
1 task done
tieujason330 opened this issue Jul 21, 2022 · 4 comments · Fixed by #2174
Closed
1 task done

Seeing empty tls_certs error when trying to run examples/complete #2171

tieujason330 opened this issue Jul 21, 2022 · 4 comments · Fixed by #2174

Comments

@tieujason330
Copy link

Description

Seeing this error when running terraform apply in terraform-aws-eks/examples/complete

╷
│ Error: Invalid index
│
│   on ../../main.tf line 211, in resource "aws_iam_openid_connect_provider" "oidc_provider":
│  211:   thumbprint_list = concat([data.tls_certificate.this[0].certificates[0].sha1_fingerprint], var.custom_oidc_thumbprints)
│     ├────────────────
│     │ data.tls_certificate.this[0].certificates is empty list of object
│
│ The given key does not identify an element in this collection value.
  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: 18.26.5

  • Terraform version: v1.0.1

Reproduction Code [Required]

Steps to reproduce the behavior:

cd terraform-aws-eks/examples/complete
terraform init
terraform apply # error appears

Expected behavior

Expected to be able to launch EKS cluster.

Actual behavior

Error above appears.

@tieujason330
Copy link
Author

looks like i opened this issue at the same time as #2170. looks to be the same issue, although my scenario isn't setting any variables

@maheimstaden
Copy link

Hi!

Have the same issue - yesterday it was not there...

Kr,
Michal.

@antonbabenko
Copy link
Member

This issue has been resolved in version 18.26.6 🎉

@github-actions
Copy link

github-actions bot commented Nov 9, 2022

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 Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants