fix(ai): correct the Context Chat embedding API key env var name - #15495
Open
bakiburakogun wants to merge 1 commit into
Open
fix(ai): correct the Context Chat embedding API key env var name#15495bakiburakogun wants to merge 1 commit into
bakiburakogun wants to merge 1 commit into
Conversation
Contributor
|
will backport this after #15491 and its backports are in. |
The documented name is CC_EM_API_KEY, but context_chat_backend reads CC_EM_APIKEY. An administrator following the docs gets an unauthenticated embedding client with no obvious sign of why. Signed-off-by: Baki Burak Öğün <63836730+bakiburakogun@users.noreply.github.com>
bakiburakogun
force-pushed
the
fix/context-chat-embedding-apikey-env
branch
from
August 30, 2026 03:49
bc5e792 to
3a98eda
Compare
Contributor
|
/backport to stable35 |
Contributor
|
/backport to stable34 |
Contributor
|
/backport to stable33 |
Contributor
|
/backport to stable32 |
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.
The Context Chat scaling section documents the embedding API key as
CC_EM_API_KEY, butcontext_chat_backendreadsCC_EM_APIKEY.In
context_chat_backend/config_parser.py:CC_EM_APIKEYappears four times across the repository;CC_EM_API_KEYappears nowhere. The other three names in the same sentence —CC_EM_BASE_URL,CC_EM_MODEL_NAME,CC_EM_USERNAME,CC_EM_PASSWORD— all match the code.The failure mode is quiet: an administrator who follows the documentation sets a variable nothing reads,
authfalls through toNone, and the backend talks to the embedding service unauthenticated. Depending on how that service answers, the first sign of trouble is an indexing failure some distance away from the cause.I hit this while setting up an on-premises embedding service for a Nextcloud 34 installation.
Only the documented name is changed here. If you would rather the code accept both spellings, I am happy to open that against
context_chat_backendinstead.