Carolyn Nguyen

Hello @brightsparc , Sorry for the late response! Thanks for bringing this to our attention - I was able to reproduce this error with the [hello_world_workflow](https://github.com/aws/amazon-sagemaker-examples/blob/master/step-functions-data-science-sdk/hello_world_workflow/hello_world_workflow.ipynb) example. Tagging it as...

Taking over to help merge @yoodan93 's PR Thank you for your review - will be addressing comments shortly

>can you also add some details around testing Added manual test details >at some point we should probably add some basic integ tests that exercise state machines and their support...

>This is very unspecific. Can you share the SDK code you used to generate that? Agreed - this is not sufficient information to reproduce the test. I provided more details...

Hi @ysgit Thank you reporting this! We are currently working on exposing the `TransformStep` `parameters` in the step constructor. With this change, any parameters documented in [CreateTransformJob](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateTransformJob.html) will be dynamically...

>I think we should also update the docs related to placeholders. Might make sense to re-purpose the example in your commit body to illustrate its usage. Agreed - will update...

>InputPath and OutputPath are allowed in all state types except Fail. Please update the PR title, description, and tests accordingly. Updated the PR title and description

Hi @Luca-Ferrera, I can see this being used by many of our customers - this will be a great feature to add to the Data Science SDK. Thank you for...

Hi @AtsunoriFujita, Sorry for the late response! Thank you for bringing this to our attention - we will need to provide a fix to have consistent behaviour with SageMaker training...

Hi @DataPsycho! Currently, the only way to use Placeholders with `container_arguments` is to define the container arguments entirely as a Placeholder. Something like this: ``` execution_input = ExecutionInput( schema={ "PATH_INPUT":...