Make token store writes atomic #1406
Merged
Conversation
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
Tejas-Kochar
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Tejas-Kochar
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Tejas-Kochar
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Tejas-Kochar
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
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 changes are proposed in this pull request?
This makes writes to the token store to avoid cache corruption from concurrent writes. It does this using write-then-rename.
How is this tested?
Existing token store tests (
credentials/u2m/cache/file_test.go).Manually tested databricks-cli auth type with existing profile, it continued to work.
NO_CHANGELOG=true