Set parent client's token on its clone - #1270
Merged
Merged
Conversation
During new entity type resource creation, the parent's token was not being set on the retry clone client. Setting the token is required since `client.Clone()` does not include the token.
benashz
force-pushed
the
VAULT-4650/fix-new-enity-read-error
branch
from
December 22, 2021 16:10
e8e3687 to
f0a1e9f
Compare
vinay-gopalan
approved these changes
Dec 22, 2021
This was referenced Dec 22, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
During new entity type resource creation, the parent's token was not
being set on the retry clone client. Setting the token is required since
client.Clone()does not include the token.Community Note
Closes #1269
Release note for CHANGELOG:
Output from acceptance testing: