Leverage camel-k as a lib

[lburgazzoli]

Requirement

Leverage camel-k as a lib

Problem

I'm working on an golang based operator that interact with camel-k, hence I want to leverage the camel-k APIs and the client, however, due to the changes related the #4686, things seems to be much more complicated than what it should be as:

• a number of indirect dependencies are eventually conflicting with local dependencies, as example the OpenShift dependencies may be problematic, however, camel-k APIs and Client should ideally not require any OpenShift library as those are only needed by the operator
• the import packages now must have the v2 in the path, like github.com/apache/camel-k/v2/pkg/client/camel/clientset/versioned which is fine according to the go spec however I don't see breaking changes in the camel-k APIs

Proposal

We should revisit the way the camel-k packages are exposed for 3rd party usage.

Open questions

No response

[github-actions[bot]]

This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!