Open njvijay-mck opened 1 year ago
Thanks for creating the issue @njvijay-mck !
Do you use the feature of parameter overriding on the SageMaker UI side? If not, then maybe we can introduce a flag to skip the translation of Kedro params to SageMaker params and just rely on the config files stored in the docker image 🤔
I am not using sagemaker UI for parameter override since I rely entirely on kedro parameters yaml file (mainly for training). It is a good idea to introduce a flag to skip. But in some cases, I depend on Kedro command parameters like --env, --pipeline
Are you willing to contribute that feature in a form of a PR?
I'd be happy to contribute, but it may take some time due to my current workload. I'll do my best to prioritize it as it is an important feature.
Awesome, let's stay in touch!
@njvijay-mck are you still willing to contribute a fix for this issue?
I'm currently using the Kedro-SageMaker plugin to run a Kedro pipeline on SageMaker. My Kedro project has multiple parameters (using several parameters YAML files).
While executing
kedro sagemaker run -i <image name>
, I encountered this error:ClientError: ValidationError for UpdatePipeline operation: Unable to parse pipeline definition. Model validation failed - container ProcessingEnvironmentMap length (132) exceeds maximum limit (100).
Here are the steps to reproduce the issue.
kedro sagemaker run --auto-build
dummy_parameter.yml file content: