-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execution inputs as container arguments for processing jobs #197
Comments
Can you elaborate on the behaviour you are seeing? |
With When I execute
This is the complete error:
On the other hand, with |
Thanks for the additional details. The problem is likely that ProcessingStep passes aws-step-functions-data-science-sdk-python/src/stepfunctions/steps/sagemaker.py Lines 558 to 561 in 02ed72b
The work should be similar to #155 With some slight differences because difference because container_arguments is an array instead of a object |
Hi @francescocamussoni did you resolve this? I'm having the exact same issue. Thanks! |
I have figured it out - the entire
And then when calling
|
I'm trying to use execution inputs as container arguements for my processing job:
I've also tried to replace container_arguments for
["--fecha", execution_input["Fecha"]]
But in both cases it doesn't work.
Use Case
When I lunch a new execution of my state machine, it would be useful to get some execution inputs as a container argument in order to define some parameters of intereset that will be define the behaviour of the step directly by the execution input without updating the state machine definition
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: