-
Couldn't load subscription status.
- Fork 787
Description
When creating a Sensor with an HTTP trigger, it is not possible to forward the incoming JSON payload directly to the downstream endpoint.
The payload section requires a dest field, but leaving it empty produces an error:
template http-trigger is invalid, payload index: 0. err: parameter destination can't be empty
This prevents sending the dependency event payload unchanged to an HTTP endpoint.
To Reproduce
Steps to reproduce the behavior:
Create an EventSource that emits a JSON payload.
Create a Sensor with an HTTP trigger, using payload with src.dataKey: body and leaving dest empty.
Apply the Sensor.
See error during validation.
Example Sensor snippet:
triggers:
- template:
name: http-trigger
http:
url: http://my-app.my-ns.svc.cluster.local:8080/v1/my-endpoint
method: POST
headers:
Content-Type: application/json
payload:
- src:
dependencyName: dt-mv-prediction-orchestrator-dep
dataKey: body
dest: "" # ❌ not allowed
Error:
template http-trigger is invalid, payload index: 0. err: parameter destination can't be empty
Expected behavior
The Sensor should allow forwarding the dependency event’s JSON payload without modification — i.e., support an option where the full body is passed directly to the HTTP request body, without requiring a dest mapping.
Environment
Kubernetes version: v1.32.2
Argo Events version: v3.6.10
Argo Workflows version: v3.6.10 (if relevant)
Additional context
The current workaround is to explicitly use dest: body, which wraps the payload correctly, but this is unintuitive and prevents forwarding the payload as-is.