Closed gilinachum closed 2 years ago
replacing export LCC_CONTENT=cat ${SCRIPT_FILE_NAME} | base64 With: LCC_CONTENT=openssl base64 -A -in ${SCRIPT_FILE_NAME} As previous command was introducing whitespaces into the base64 string (tested on a SageMaker Studio notebook terminal). Now it's also inline with the command suggested in the blog post: https://aws.amazon.com/blogs/machine-learning/customize-amazon-sagemaker-studio-using-lifecycle-configurations/
cat ${SCRIPT_FILE_NAME} | base64
openssl base64 -A -in ${SCRIPT_FILE_NAME}
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
replacing export LCC_CONTENT=
cat ${SCRIPT_FILE_NAME} | base64
With: LCC_CONTENT=openssl base64 -A -in ${SCRIPT_FILE_NAME}
As previous command was introducing whitespaces into the base64 string (tested on a SageMaker Studio notebook terminal). Now it's also inline with the command suggested in the blog post: https://aws.amazon.com/blogs/machine-learning/customize-amazon-sagemaker-studio-using-lifecycle-configurations/Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.