-
Notifications
You must be signed in to change notification settings - Fork 981
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
Error: Value Conversion Error - crashes terraform plan #2388
Comments
CloudPosse helped me fix this, via their SweetOps Slack workspace. I had to declare and pin kubernetes provider to
Feedback was a new provider framework, that does not support computed lists. I will close this out as I have a solution, hopefully that will help others. Big shout out to CloudPosse for the help! I was pretty stuck on this the past day 🙃 |
@adampeklay Thanks for documenting this. I was getting the same error for exactly the same reason. |
@adampeklay Please re-open this issue. You have a workaround for it, not a fix. The fix needs to be made by Hashicorp so that their provider does not crash. |
We are affected by this issue as well the mentioned bug appeared in 2.25.0 for us and persists in 2.26.0 |
Terraform Version, Provider Version and Kubernetes Version
Terraform version:
1.6.6
I've also tried all of these versions, same error:
AWS provider version:
5.31.0
EKS Version
1.28
Affected Resource(s)
EKS cluster
Terraform Configuration Files
Steps to Reproduce
terraform plan
Expected Behavior
What should have happened?
terraform plan
succeedsActual Behavior
What actually happened?
terraform plan
failsImportant Factoids
This was working just fine on Tuesday, then I got busy Wednesday with unplanned work, then Thursday this started bombing out.
.kubernetes.d
, there was no lock to remove, I even deleted the workspace directories too. No luck.tfvars
but that was not the issue eitherdummy_kubeapi_server = null
per information in (from error message):That did not help
Please let me know if you need any additional information, thank you!
The text was updated successfully, but these errors were encountered: