[Fix] Multi Auth Token issue #51
Merged
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.
🐞 Bug Fix: Multi Auth Token Issue
🧾 Summary
Fixes the Multi Auth Token issue when mutliple URLs, auth_tokens are provided
Previously, models inconsistently used
api_keyandauth_token, leading to authentication mismatches.This PR ensures consistent use of
auth_tokenfor all model configurations, improving reliability and maintainability.💡 Impacted Features:
.envwith|separator can be providedMinor Fixes:
api_keyforazure_openaito make it consistent with other model types.api_key->auth_tokenmodels.yaml,model_configuration.md)🧪 How to Test
Steps for reviewers to verify functionality:
.envwith|separator.Screenshots (if applicable)
N/A
Checklist
Notes
NO CHANGES NEEDED FROM USER END