using ${data} in header/body does not work

[amalaguti]

I have the following header using a parameter from ${data}, this does not work
X-Xsrftoken: ${data.xsrf}

Just read the TODO: Support request parameters from config and/or data

Wondering if there are plans to support it ?

[palto42]

I faced the same issue and found that it seems to partially work.
I have two data variables, one extracted from a previous http-step result using jq log filter, and the second extracted from bash script also with jq log filter.
The first data value is inserted in URL of the http-step, but the second is always blank.
I can use both values in a later shell script step.

I tested this with latest http-step version 1.1.6

[palto42]

@amalaguti I fixed it for my use case.

The problem is that you can use the http-step as "node step" or "workflow step".
The script step I used to create extra data, is always a "node step" and it's not possible to pass data between a workflow step and a node step.

After changing the http-step to be from the category "node-step" to pass the data generated by some other "node type step".