Disabling the SageMaker Specific Post Startup Scripts #805
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Disabling the SageMaker Specific Post Startup Scripts
Type of Change
Release Information
Does this change need to be included in patch version releases? By default, any pull requests will only be added to the next SMD image minor version release once they are merged in template folder. Only critical bug fix or security update should be applied to new patch versions of existed image minor versions.
If yes, please explain why:
We do not want the SMUS Post start up scripts to show in the SMAI, so we need this change merged.
How Has This Been Tested?
The test was to check if the Post start up Scripts show in the SMAI image and it doesn't show up
Checklist:
Test Screenshots (if applicable):
Additional Notes
This is to update the Disable the SageMaker Specific Post Startup Scripts to so they wouldn't be invoked in the SMAI images.