Conversation
vdice
force-pushed
the
feat/auto-detect-provider
branch
3 times, most recently
from
9a68cc2 to
e816765
Compare
lann
approved these changes
Mar 25, 2026
Signed-off-by: Vaughn Dice <vdice@akamai.com>
vdice
force-pushed
the
feat/auto-detect-provider
branch
from
e816765 to
c214974
Compare
Member
Author
|
The amended commit just re-adds the |
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.
Updates this utility to automatically detect the correct (supported) provider based on each token provided.
In doing so, I refactored things; mostly moving token checking and request logic closer to each provider, with base implementations that can be used if special logic is not needed.
As of the latest commit, this is a breaking change, as it drops the
--providerflag/arg. If we like the looks of this change but would rather not break things, it shouldn't be too hard to add it back, perhaps with a deprecation warning. Thoughts?