-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
MGDOBR - Sprint 224, MGDOBR - Sprint 225, MGDOBR - Sprint 227, MGDOBR - Sprint 228, MGDOBR - Sprint 229
Issue Description:
We should provide a new kind of processor based on Camel that supports content based routing and multiple actions. See the document for the syntax and https://issues.redhat.com/browse/MGDOBR-877 https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/922 for POC code
Document for Camel POC https://docs.google.com/document/d/1kgrR-bJcL23AdrDVVKCxGHx3WSZWufL9kMZwEiAsMeU/edit#bookmark=id.d95u97n0ku8i
Acceptance Criteria:
- Expose a new API under /v2 that allows a customer to submit their Processor definition using Camel DSL
- The /v1 API for creating a Processor must remain fully functional
- It should be possible to create a new Camel processor, without it being provisioned by the Operator
Out of Scope:
- Deploy the CamelK resource
- is blocked by
-
MGDOBR-1106 API versioning: Manager services and models
- Closed
-
MGDOBR-1107 API versioning: Operator CRD, Controller and models
- Closed
- is cloned by
-
MGDOBR-1012 Support new type of Camel Processor for sources, control plane - (Camel DSL / KNative integration)
- Closed
- is depended on by
-
MGDOBR-1006 Let Shard provision Camel Processor, data plane - (Camel DSL / KNative integration)
- Closed
- relates to
-
MGDOBR-877 POC on Camel DSL / KNative integration
- Closed