Describe the feature you'd like
Allow for sagemaker.core.shapes.ProcessingInput to accept local file path as input, for automatic uploading of input files to S3.
How would this feature be used? Please describe.
When migrating from sagemaker v2 to v3, the sagemaker.processing.ProcessingInput used in sagemaker.workflow.steps.ProcessingStep.inputs() is no longer applicable, replaced by sagemaker.core.shapes.ProcessingInput used in sagemaker.core.processing.ScriptProcessor.run(). sagemaker.core.shapes.ProcessingInput accepts only S3 path, which makes it more convoluted for the training pipeline process as the files involved in the pipeline have to be uploaded separately before the creation of the pipeline, instead of how it was done in v2's sagemaker.processing.ProcessingInput which uploads it while the pipeline is being built.
Describe the feature you'd like
Allow for
sagemaker.core.shapes.ProcessingInputto accept local file path as input, for automatic uploading of input files to S3.How would this feature be used? Please describe.
When migrating from sagemaker v2 to v3, the
sagemaker.processing.ProcessingInputused insagemaker.workflow.steps.ProcessingStep.inputs()is no longer applicable, replaced bysagemaker.core.shapes.ProcessingInputused insagemaker.core.processing.ScriptProcessor.run().sagemaker.core.shapes.ProcessingInputaccepts only S3 path, which makes it more convoluted for the training pipeline process as the files involved in the pipeline have to be uploaded separately before the creation of the pipeline, instead of how it was done in v2'ssagemaker.processing.ProcessingInputwhich uploads it while the pipeline is being built.