fix(rag): restore private dependency build credentials - #70
Merged
Conversation
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
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.
Summary
PR #64 removed the RAG build secret and build arguments based on an incorrect assumption that the current Dockerfile no longer used private dependencies. The backend stage still installs pinned private git+https dependencies (omnibioai-iam-client and omnibioai-usage-client) through a BuildKit github_token mount. The UI stage separately installs private @OmniBioAI packages through its existing GITHUB_TOKEN npm argument.
This forward fix restores only:
It does not restore the removed RAGBIO_API_KEY build argument.
Verification
No force-push or history rewrite.