Ability to plugin additional containers#162
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
Greptile SummaryThis PR adds experimental plugin MCP containers alongside the existing vault container. The main changes are:
Confidence Score: 5/5This looks safe to merge. No blocking issues found in the changed code.
What T-Rex did
Important Files Changed
Reviews (2): Last reviewed commit: "address greptile feedback" | Re-trigger Greptile |
| fn resolve_plugin_host_port(plugin: &PluginMcpContainerConfig) -> Result<u16, ContainerError> { | ||
| match plugin.host_port { | ||
| Some(port) => Ok(port), | ||
| None => pick_free_loopback_port().map_err(|error| { | ||
| ContainerError::Other(format!( | ||
| "failed to pick host port for Plugin MCP Container '{}': {error}", | ||
| plugin.name | ||
| )) | ||
| }), | ||
| } |
There was a problem hiding this comment.
Drop plugin Docker/macOS-container MCP servers (e.g. a for prototyping) next to the existing core vault container. Currently via via a hand-edited config file only.