Disallow TLS provider v4 due to provider issue 244 #158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/test all |
Nuru
changed the title
|
/test all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
hashicorp/tlsprovider version >= 4.0.0why
When using
hashicorp/tlsprovider v4.0.0 and settingoidc_provider_enabled = trueon a new EKS cluster deployment,terraform planwill fail withthumbprint_list = [join("", data.tls_certificate.cluster.*.certficates.0.sha1_fingerprint)]andThe given key does not identify an element in this collection value: the collection has no elements.references