You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/08/03 15:47:32 UTC
[GitHub] [camel-k] hguerrero opened a new issue #1650: Add the option to deploy a CamelSource Integration from the CLI
hguerrero opened a new issue #1650:
URL: https://github.com/apache/camel-k/issues/1650
The Kamel CLI should be able to manage and deploy CamelSource knative sources.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] github-actions[bot] commented on issue #1650: Add the option to deploy a CamelSource Integration from the CLI
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1650:
URL: https://github.com/apache/camel-k/issues/1650#issuecomment-994157995
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!
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1650: Add the option to deploy a CamelSource Integration from the CLI
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1650:
URL: https://github.com/apache/camel-k/issues/1650#issuecomment-668599707
They are currently part of knative, that's the reason why they are not here. Also `kubectl` can deploy them just fine..
But we can consider it when we decide the long-term strategy for CamelSources.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] hguerrero commented on issue #1650: Add the option to deploy a CamelSource Integration from the CLI
Posted by GitBox <gi...@apache.org>.
hguerrero commented on issue #1650:
URL: https://github.com/apache/camel-k/issues/1650#issuecomment-668646497
how is that working? I was envisioning more take a camel k integration and conver that into a camelsource and deploy as it instead of as an integration
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] github-actions[bot] closed issue #1650: Add the option to deploy a CamelSource Integration from the CLI
Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #1650:
URL: https://github.com/apache/camel-k/issues/1650
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1650: Add the option to deploy a CamelSource Integration from the CLI
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1650:
URL: https://github.com/apache/camel-k/issues/1650#issuecomment-669071105
> how is that working? I was envisioning more take a camel k integration and conver that into a camelsource and deploy as it instead of as an integration
What you describe is (almost) the approach taken in the experimental PR #1637, where we take an integration and create a child sinkbinding, which is interpreted by Knative as a source.
The current approach instead is that a (knative) CamelSource is created via kubectl and it creates a child Integration that runs the code.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org