-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: Propagate tags and VPC configs to repack model steps #2594
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
fix: Propagate tags and VPC configs to repack model steps #2594
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue #, if available:
#2302
Description of changes:
Adding a RegisterModel step to a pipeline causes a RepackModel step to be automatically added if the model has a custom entry point. Tags and VPC configs from the RegisterModel step are not being propagated to the RepackModel step, causing problems for network isolated users.
Propagate tags as well as VPC config to the Repack step. The VPC config will be pulled either from the estimator, model, or pipeline model passed to the RegisterModel step.
Testing done:
Manual, unit
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.General
Tests
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.