luigidemasi commented on issue #7: URL: https://github.com/apache/camel-kit/issues/7#issuecomment-6336759240
> Comment by [gnodet](https://github.com/gnodet) on 2026-03-11 ([original](https://github.com/luigidemasi/camel-kit/issues/1#issuecomment-4039764342)). --- Hi @orpiske, I'm looking at contributing Wanaku support and wanted to make sure we understand the use case correctly before building the wrong thing. Based on this issue, it sounds like you'd want a new command (e.g., `/camel-wanaku` or a `camel-kit export --wanaku` flag) that takes a generated Camel route (from `/camel-implement`) and: 1. **Packages the route for the Wanaku Camel Integration Capability** — so it can be deployed as a capability service behind the Wanaku router 2. **Generates the exposure rules file** — defining how the route's endpoints are exposed as MCP tools (tool name, description, input parameters, URI mapping) A few questions: - Is the "Camel Integration Capability" the [camel-capability](https://github.com/wanaku-ai/wanaku) module, or something else? Any pointers to docs on the expected route format? - For the exposure rules — is this the `wanaku tools add` equivalent as a file, or a different format? - Should this also handle registering the route with a running Wanaku instance (via CLI/API), or just generate the artifacts? I've started with a minimal plugin scaffold (`camel-kit-plugins/camel-kit-wanaku-plugin/`) but want to align on the right approach before going further. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
