feat: lock auth flow #138
Merged
feat: lock auth flow #138
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
Signed-off-by: Tim Heurich <[email protected]>
Signed-off-by: Tim Heurich <[email protected]>
Signed-off-by: Tim Heurich <[email protected]>
fixes #130 Signed-off-by: Tim Heurich <[email protected]>
Signed-off-by: Tim Heurich <[email protected]>
theurichde
force-pushed
the
feat/lock-auth-flow
branch
from
ee3f3fd
to
4b64ab5
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.
I came across this issue when using the k8s plugin for IntelliJ - opening around 75 tabs at the same time, asking for approval when the access token was outdated while using the credentials_process mode. So we lock the authorization flow now to one concurrent flow at a time.