Closed sebastianrosch closed 5 years ago
Hi @sebastianroesch - thanks for raising the issue. This might be a 'bug' in the javascript expression evaluator: it is an invalid field name in javascript. $.Invocation.Inputs.headers['X-B3-Traceid']
should work.
Regardless, it is indeed something that we should catch earlier on in validation 👍
$.Invocation.Inputs.headers['X-B3-Traceid']
works for me, thank you!
The workflow definition does not allow me to access header fields that contain a dash, like
X-B3-Traceid
. Workflow execution fails withparse error: Invalid literal at line 1, column 7
My workflow:
Workflow validation succeeds.
This is the output of
$.Invocation
, so the$.Invocation.Inputs.headers.X-B3-Traceid
field exists.