-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate overlapping Kamel CLI features in favour of Camel JBang #3790
Comments
In general I'm in favor to go in that direction. However, for |
* kamel local * kamel init Closes apache#3790
I've added a PR that will address this issue. However, I have some remarks.
|
Thanks! Yes, I agree that For For The reason why I'd think the subcommand is useful for debugging is that it uses the same internal mechanism with Different views are also welcome. |
You can use |
Ah cool. |
* kamel local * kamel init Closes apache#3790
* kamel local * kamel init Closes #3790
There are overlapping features between Camel K
kamel
CLI and Camel JBang. To name a few:kamel init
vscamel init
kamel local run
vscamel run
kamel bind
vscamel bind
We should favour
camel
overkamel
for the overlapping features and drop them fromkamel
for Camel K 2.0. For now, we should mark them as deprecated.The text was updated successfully, but these errors were encountered: