Comments (3)
We definitely need to support REST
or http
signals and triggers. In terms of the signals, do we need to consider which port to expose the endpoint on? Furthermore, to extend this feature to other applications on K8s and even outside K8s, these webhook signals should have a service
that exposes them. Thoughts?
from argo-events.
Also, I understand the motivation behind including the trigger
reference in the signal specification, but this shouldn't change the core concept that all signals must be resolved for any trigger to execute. I think what you intended this to be was for each of these signals' payload or content would act as input to the corresponding trigger. If this is the case, this should be generalized for not just webhook
signals, this can be applicable for any type of signal that carries a message/artifact/content... (basically anything except time, in fact time seems to be a special case here).
from argo-events.
closing this from merged PR #15
from argo-events.
Related Issues (20)
- EventSensor DLQ after retry exhaustion HOT 1
- AMQP trigger support
- Updating a Workflow While It's Running Spawns Multiple Workflows HOT 1
- failed to get value by key: key body.message does not exist to in the event payload HOT 1
- Allow namespace-scoped permissions when doing a cluster-level install HOT 1
- Unable to delete a cluster scoped resource HOT 1
- Finish the field specifications in the EventBus CRD HOT 1
- Provide option to disable TLS in NATS
- Support AWS EventBridge
- Support NATS Jetstream Consumer as EventSource
- HTTP Trigger Support Multipart/form-data encoding
- Allow Configurable Retention and Discard Policies for Jetstream EventBus
- Sensor high memory consuming / Low event processing throughput
- Sensor does not support automountServiceAccountToken
- Nats Jetstream Support in EventSource HOT 2
- A workflow works with argo workflows cli/ui/kubectl but not with argoworkflows sensor
- Kustomizations don't comply with kubernetes recommended labels
- Enhance HTTP Method Handling to Integrate Query Parameters, Headers, and Body for Webhook Events HOT 1
- bitbucket server eventsource regressions HOT 4
- Update Sensor and EventSource CRDs to support Vertical Pod Autoscaler HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from argo-events.