Bug/plat 655/kb database host path change not applied on update#416
Bug/plat 655/kb database host path change not applied on update#416moizpgedge wants to merge 2 commits into
Conversation
KB config changes (path, provider, model, key) had no effect after an update: config.yaml is bind-mounted so SIGHUP-only reload kept the old KB path, causing "file not found" / SQLite errors. Embed a PGEDGE_CONFIG_VERSION hash in the MCP container env (like RAG) so a config change forces a restart and re-initializes the KB. Also refresh the service instance's UpdatedAt before an update redeploy so the monitor doesn't briefly mark it failed during the restart.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR introduces two independent changes to the swarm orchestration package: (1) a ChangesserviceConfigHash Unification for MCP and RAG
Pre-deploy UpdatedAt Refresh
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
kb_database_host_path pointing at a directory passed the deploy-time existence check (afero.Exists is true for directories), so the service deployed and only failed later at query time when MCP tried to open the directory as a SQLite database.
checkKBFileExists now rejects a directory with a clear error at deploy time, and a regression test covers it.
plat-662