luigidemasi commented on issue #7: URL: https://github.com/apache/camel-kit/issues/7#issuecomment-6336760125
> Comment by [orpiske](https://github.com/orpiske) on 2026-03-11 ([original](https://github.com/luigidemasi/camel-kit/issues/1#issuecomment-4041299816)). --- > Hi [@orpiske](https://github.com/orpiske), I'm looking at contributing Wanaku support and wanted to make sure we understand the use case correctly before building the wrong thing. Thanks for looking at this 🙏 > > 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: That's pretty much it. > > 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? The Camel Integration Capability is [this one](https://github.com/wanaku-ai/camel-integration-capability). There are some documents in the docs folder in that project, but I think the [usage guide](https://github.com/wanaku-ai/camel-integration-capability/blob/main/docs/usage.md) should be the most adequate one. The documentation should be mostly up to date, except maybe, for details about running the plugin for existing Camel integrations. > > * For the exposure rules — is this the `wanaku tools add` equivalent as a file, or a different format? The exposure rules is the equivalent of running `wanaku tools add` or `wanaku resources expose`, however that step is not necessary in Camel Kit because the Camel Integration Capability instance adds the tools/resources automatically after reading that file from the data store. So, Camel Kit doesn't really need to do anything here. > * Should this also handle registering the route with a running Wanaku instance (via CLI/API), or just generate the artifacts? Camel Kit can just generate the artifacts and upload them. > > 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. I think this is in the right track -- 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]
