Skip to content

_RepackModelStep doesn't inherit Environment Variables #3545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jmgray24 opened this issue Dec 16, 2022 · 2 comments
Closed

_RepackModelStep doesn't inherit Environment Variables #3545

jmgray24 opened this issue Dec 16, 2022 · 2 comments
Labels
component: pipelines Relates to the SageMaker Pipeline Platform type: question

Comments

@jmgray24
Copy link

We have a proxy configured for HTTP/HTTPS. When the model repack step runs, it doesn't inherit the environment variables from the model, causing the ModelRepack to fail. This should pass through environment variables defined from the Model.

repack_model_step = _RepackModelStep(

@jmgray24
Copy link
Author

The pip install step was removed in #3143, so we should be unblocked by incrementing our version in our CI/CD pipelines, but repack should inherit any environment variables in order to appropriately respect customers configuration (i.e. proxy),

@qidewenwhen qidewenwhen added component: pipelines Relates to the SageMaker Pipeline Platform type: question labels Dec 23, 2022
@qidewenwhen
Copy link
Member

Hi @jmgray24, thanks for reaching out!

The repack step is an additional helper step for a CreateModel/ RegisterModel step. The repack step is only used for simply repacking custom dependencies and inference script into an existing model TAR archive, so that the new repacked model can be used in the subsequent CreateModel/ RegisterModel step. In other words, the environment variables do not take any effect in a repack step AFAIK. And as you already pointed out, it was the pip install issue in #3143 that caused your repack step to fail, rather than the env vars, as upgrading the sagemaker sdk version unblocked you.

On the other hand, customer environment variables are passed to the CreateModel/ RegisterModel step directly so you'll see the env variables in the Model/ModelPackage console. I did a quick test and can verify that customer env vars were correctly displayed there.

Please let me know if this answer helps you. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: pipelines Relates to the SageMaker Pipeline Platform type: question
Projects
None yet
Development

No branches or pull requests

2 participants