-
Enhancement
-
Resolution: Done
-
Major
-
1.34.0.Final
-
None
-
False
-
None
-
False
-
---
-
---
-
-
-
2023 Week 12-14 (from Mar 20), 2023 Week 15-17 (from Apr 10), 2023 Week 18-20 (from May 1)
Although is not published yet, we should implement the initial draft of the Knative Functions definitions in the workflow: https://hackmd.io/caIcNikDSASCxTX51QJ53w:
- name: processOrder operation: knative:services.v1.serving.knative.dev/default/processOrder?path=/init&asCloudEvent=false type: custom
And to invoke the function:
functions: - name: processOrder operation: knative:services.v1.serving.knative.dev/default/processOrder?path=/init&asCloudEvent=false type: custom states: - name: send event type: operation actions: functionRef: refName: processOrder arguments: type: com.hospital.patient.heartRateMonitor source: hospitalMonitorSystem id: ${ } data: ${ . }
This is just an adjustment in the interface. Internally, it should work as it's today with discovery in-place based on the object definition.
- is blocked by
-
KOGITO-8409 [SW] Add support to Cloud Events to Knative custom function
- Resolved
- is related to
-
KOGITO-8770 [SPIKE] [SW] Reassess the Kubernetes/Knative discovery and internal catalog to keep them independent
- Resolved
- relates to
-
KOGITO-8313 [Operator] Knative Functions discovery in the Serverless Operator
- Closed
There are no Sub-Tasks for this issue.