Repository navigation
feat: add engine key ring with lazy tenant keys, deadlines and reconnect - #138
Merged
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
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.
keys::Ringper core: lazy single-flightOpen, bounded clock cache of working keys, call deadlines (short for open and unwrap, long for vault writes), reconnect with backoff,Helloon every connect; a changed naming key fails the ring and clears its cache.Helloprobe also fails.Client::closeshuts the stream down; a dropped client closes its connection.sched::Keyringadapts the ring toKeySource.KeyError::Failed: a failed ring or vault fails start instead of waiting.Refusal::Keysand counts them apart.Part of #129