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

aws_eks_cluster output of certificate failing #6077

Closed
Artemu opened this issue Oct 5, 2018 · 3 comments
Closed

aws_eks_cluster output of certificate failing #6077

Artemu opened this issue Oct 5, 2018 · 3 comments
Labels
upstream-terraform Addresses functionality related to the Terraform core binary.

Comments

@Artemu
Copy link

Artemu commented Oct 5, 2018

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.11.8

Affected Resource(s)

  • aws_1.38.0

Terraform Configuration Files

provider "aws" {
  region = "eu-west-1"
  shared_credentials_file = "~/.aws/credentials"
  profile                 = "test"
}

Debug Output

* module.eks-staging.output.cluster: Resource 'aws_eks_cluster.cluster' does not have attribute 'certificate_authority.0.data' for variable 'aws_eks_cluster.cluster.certificate_authority.0.data'

https://gist.github.com/Artemu/ea2f4f83324837d9a59f76a75c82896f
The above output is from the endpoint but all outputs giving issues.

Expected Behavior

When the resource is deleted, Terraform should not fail because the resource does not exist.

Actual Behavior

Once the resource is deleted, Terraform is unable to run. The output has to be commented out to complete the terraform destroy function in two stages.

Steps to Reproduce

  1. Generate an EKS resource
  2. Delete it with the output present.
output "cluster" {
  value = {
    eks_endpoint              = "${aws_eks_cluster.cluster.endpoint}"
    eks_certificate_authority = "${aws_eks_cluster.cluster.certificate_authority.0.data}"
}

Important Factoids

None

References

As per documentation: https://www.terraform.io/docs/providers/aws/r/eks_cluster.html

@bflad
Copy link
Contributor

bflad commented Oct 5, 2018

Hi @Artemu 👋 Sorry you are running into this difficulty. I believe the behavior here is actually not specific to this resource or this provider, but rather managed by Terraform core which handles the dependency graph and outputs. I think this upstream issue is relevant (or there may be other similar/more pertinent ones): hashicorp/terraform#18026

I would suggest commenting and/or 👍 upvoting the issue report(s) upstream. Since I'm not sure there's anything to be done with the resource or provider, I am going to close out this issue here.

@bflad bflad closed this as completed Oct 5, 2018
@bflad bflad added the upstream-terraform Addresses functionality related to the Terraform core binary. label Oct 5, 2018
@Artemu
Copy link
Author

Artemu commented Oct 5, 2018

Thanks :) Will follow that issue; was under the presumption it was a provider issue.

@ghost
Copy link

ghost commented Apr 3, 2020

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!

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream-terraform Addresses functionality related to the Terraform core binary.
Projects
None yet
Development

No branches or pull requests

2 participants