Open jaymed opened 5 years ago
Hello, @jaymed
You can't use ${}
syntax in _export
part in the current implementation.
I'll add more detail later.
seems like same issue as https://github.com/treasure-data/digdag/issues/678 or https://github.com/treasure-data/digdag/issues/862 ?
seems like same issue as #678 or #862 ?
Thanks, @chezou. It's exactly like #678. I'll have to come up with a different way to pass nested parameters to my python function.
I'm also finding that secrets can't be evaluated as py
parameters, even if they aren't nested.
+setup:
py>: tasks.MyWorkflow.step1
arg1: ${secret:password}
Without the ability to pass in dates from _export
data or secrets to py
operators, I'm really limited in what I can do with digdag
.
I'm trying to call a python task with a parameter that contain a list of dictionary values by using
_export
variables. The variables used to define the values in the list of dictionaries are not being interpolated.Please consider the following example. In this case I would like
arg2
to be an array of dictionary values. In this case thearg1
param evaluates correctly but the value ofsubarg2
contains the literal definition ofrelevant_date
instead of the interpolated value.The output looks like this:
The sample python task looks like this:
Please help me understand how I can properly interpolate the value of
subarg2
.