Introduce embedding provider switcher and full switch to Voyage AI for CI/CD#214
Merged
Conversation
toptobes
approved these changes
Jul 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
…er header requirements
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
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.
This PR introduces a clean, centralized layer to switch the choice of the secret-requiring embedding provider for use in the CI/CD testing. Now it's VoyageAI.
(Apart from the nvidia embedding provider, that is, which is still hardcoded for some Astra-only tests and does not require secrets to be provided, via kms or otherwise)