Mitigate against token replication lag #102
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
pglass
force-pushed
the
pglass/mitigate-token-replication
branch
from
5d73386 to
0d3e19c
Compare
pglass
commented
Apr 28, 2022
cthain
approved these changes
Apr 28, 2022
pglass
force-pushed
the
pglass/mitigate-token-replication
branch
from
0d3e19c to
d821b2c
Compare
pglass
force-pushed
the
pglass/mitigate-token-replication
branch
from
d821b2c to
4f98aec
Compare
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.
Changes proposed in this PR:
Copy the approach from hashicorp/consul-k8s#887 for dealing with inherent token replication lag.
See: hashicorp/consul-ecs#79
How I've tested this PR:
Acceptance tests
How I expect reviewers to test this PR:
👀
Checklist:
CHANGELOG entry addedn/a