You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (Jira)" <ji...@apache.org> on 2020/07/08 06:23:00 UTC
[jira] [Commented] (CAMEL-15275) Create camel-kantive component in
main Camel components based on camel-kantive for camel-k
[ https://issues.apache.org/jira/browse/CAMEL-15275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153264#comment-17153264 ]
Luca Burgazzoli commented on CAMEL-15275:
-----------------------------------------
[~omarsmak] it is planned but may take a while as we need to consolidate some bits before moving in the main camel repo
> Create camel-kantive component in main Camel components based on camel-kantive for camel-k
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-15275
> URL: https://issues.apache.org/jira/browse/CAMEL-15275
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 3.4.0
> Reporter: Omar Al-Safi
> Priority: Minor
>
> Currently we have [{{camel-kantive}} component|https://github.com/apache/camel-k-runtime/tree/master/camel-knative] in camel-k that enables camel routes deployed in with camel-k to interact with knative components like eventing. However, currently it is only exclusive to camel-k, hence it will make sense to bring/create this component as part of the main Camel components in order in order to enable non-camel-k routes that deployed with knative (e.g: camel-quarkus, camel-spring-boot) to utilize and interact in kantive.
> FYI [~davsclaus] [~lb]] thoughts on this? I recall there was some discussion on brining this component to main Camel components.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)