You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I send named_parameters as part of my dbx execute, I want the workflow to use these parameters during runtime. This is already the case if I simply use just the normal positional parameters.
Current Behavior
DBX only parses that keys from the dict and not the values when it formats the arguments used by the task. It always assumes that a list of strings are sent as CLI arguments similar to what you would expect for positional parameters. The source code that performs this formatting is referenced here.
Steps to Reproduce (for bugs)
Create a workflow with that uses python wheel for a task (ensure that you have named_parameter as part of the workflow definition.
Expected Behavior
Whenever I send
named_parameters
as part of mydbx execute
, I want the workflow to use these parameters during runtime. This is already the case if I simply use just the normal positional parameters.Current Behavior
DBX only parses that keys from the dict and not the values when it formats the arguments used by the task. It always assumes that a list of strings are sent as CLI arguments similar to what you would expect for positional parameters. The source code that performs this formatting is referenced here.
Steps to Reproduce (for bugs)
named_parameter
as part of the workflow definition.Context
I am using a working with workflows using python wheels as tasks.
Your Environment
The text was updated successfully, but these errors were encountered: