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
First: Thanks for this api. Its really a handy way to create workflows.
Problem
We tried use an execution input for the image_uri in a Processor. The workflow ended up using the execution_input variable as a String for image_uri. It did not replace it.
In general we want to set a lot of properties via a configuration, without changing the workflow.
We would like to be able to use execution inputs for all processors and steps. The workaround is not that complicated and we do it for some values right now, but it clutters up the code.
We did not find documentation which processor properties can handle placeholers. We would really appreciate a documentation for that. Right now the stepfunctions documentation only refers to the regular sagemaker documentation.
The text was updated successfully, but these errors were encountered:
First: Thanks for this api. Its really a handy way to create workflows.
Problem
We tried use an execution input for the
image_uri
in a Processor. The workflow ended up using the execution_input variable as a String for image_uri. It did not replace it.In general we want to set a lot of properties via a configuration, without changing the workflow.
Here is what we did
Sadly the workflow did not replace
execution_input['image_uri']
with the actual value.This is our workaround
used dependencies:
Expectation
The text was updated successfully, but these errors were encountered: