Add provider argument: ca_cert_bytes #1565
Open
+16
−0
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
|
What on earth would it take to get this merged? It's almost 2025. The provider should have supported this years ago! |
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.
Community Note
Closes #1453
Release note for CHANGELOG:
Output from acceptance testing: https://gist.github.com/czembower/a44b842c494c0de75433daecd71aef80
Made possible by: hashicorp/vault@2130948
Followed naming precedent set in Vault core: VAULT_CACERT_BYTES
This feature makes it easier to use validated TLS in ephemeral run environments where the CA data is not installed locally, but available from a Terraform data source.