Add ability to optionally clone a Client's token #13515
Merged
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
vinay-gopalan
approved these changes
Dec 22, 2021
heppu
pushed a commit
to heppu/vault
that referenced
this pull request
Jan 13, 2022
joatmon08
pushed a commit
that referenced
this pull request
Jan 25, 2022
qk4l
pushed a commit
to qk4l/vault
that referenced
this pull request
Feb 4, 2022
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.
In the Vault Provider we have three separate instances where we clone the parent's token. This PR should make it simpler for us to handle this use case, and provide a more consistent experience in the provider.
Relates to hashicorp/terraform-provider-vault#1270