fix(compose): pass LORE_API_KEY to the lore service (out-of-box provisioning)#15
Merged
Conversation
…ovisioning The lore service got no LORE_API_KEY, so a Postgres-backed Lore came up with no org and no API key — every call 401'd, including AgentLens→Lore, even though health was green. Pair with lore's new LORE_API_KEY root-key seeding: the lore service now receives the same shared key AgentLens uses, so the stack is usable without a manual POST /v1/org/init. (Effective once the lore image carrying the seeding ships to ghcr :latest; harmless on the current image, which ignores it.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019tXZpN29akdmG8AEjgSZwk
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
1 participant
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
loreservice got noLORE_API_KEY, so a Postgres-backed Lore came up with no org/key — every call 401'd (including AgentLens→Lore) despite green health. Pairs with lore's newLORE_API_KEYroot-key seeding (agentkitai/lore#92): the service now gets the same shared key AgentLens uses, so the stack works without a manualPOST /v1/org/init. Harmless on the current image (ignores it); effective once the seeding image ships toghcr :latest.