Improve Dependency Handling

[orpiske]

Improve Dependency Handling

Objective

Implement dependency pre-caching mechanism via CLI to improve code execution performance by avoiding runtime dependency downloads.

Dependencies

None (independent enhancement)

Requirements

• Design cache strategy (Maven local repo, custom cache, or container images)
• Implement CLI commands for dependency pre-caching
• Support specifying dependencies via configuration or manifest
• Handle dependency resolution and download
• Integrate cache with Camel code execution runtime
• Verify cached dependencies are used during code execution
• Document CLI usage for dependency management

Affected Files/Modules

• /backend/router/src/main/java/ai/wanaku/router/cli/ (CLI commands - may need new classes)
• /backend/router/src/main/java/ai/wanaku/router/bridge/CodeExecutionBridge.java (potential integration point - needs investigation)

Notes

Consider security implications of caching dependencies. Evaluate options: (1) Maven local repository reuse, (2) custom cache directory, (3) pre-built container images with dependencies. Performance vs. flexibility tradeoff. CLI should support bulk operations and individual dependency caching.

[Croway]

Hi @orpiske I do not fully get why this is needed:

Wanaku uses AutoResolution to download the dependencies at runtime. From the issue description I can see that it should be used to avoid runtime dependency downloads. But I do not understand how an user is supposed to interact with it.

I was thinking to develop CLI commands ala cache add $LIST_OF_DEPENDENCIES but I do not think it will be used.. or at least, I do not see myself using it, I can wait few more seconds on the first run

[orpiske]

Just, for the record, as @Croway and I discussed about this on a different occasion: this is related to custom, private and/or non-Camel dependencies. There's still some details to be sorted out, but overall, the idea is to make it simple for others to use their own private repos and access those dependencies.