Avoid triggering new "conflicts with" rule in 2.21.0 Kubernetes provider #189
Conversation
…path not enabled, instead of an empty string; avoids triggering new conflictsWith rule
There was a problem hiding this comment.
I would like to put this on hold. This change removes the override of environment variables, which ensured that Terraform was targeting the correct cluster.
This change was made necessary because version 2.21.0 of the Kubernetes provider introduced a breaking change in a minor version. History suggests it will be rolled back or otherwise mitigated, so I would like to wait and see what the next release holds before making changes. I would prefer a solution (not obviously available in 2.21.0) that maintains the override behavior, and hopefully the next release will provide that.
Meanwhile, you can pin your provider version by adding != 2.21.0 to avoid this issue.
|
Please note, after feedback received, a hot fix of the Kubernetes provider for Terraform has been released to revert the breaking change that introduced this: (v2.21.1) - we will reconsider this for our next major release. |
|
Closing because this was caused by a breaking change in the provider, which has since been rolled back. |
Closes #188
what
Avoids triggering the "conflicts with" error that now crops up with the latest version (2.21.0) of the Kubernetes provider.
why
Terraform actions involving this module and the latest Kubernetes provider fail.
references
https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.21.0
hashicorp/terraform-provider-kubernetes#2084