-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: use the provided kms key to upload user code #2005
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
Conversation
Somehow the kms key fix aws#1897 that was recently merged is not propagate throughout all the methods that require itt when uploading customer code for example, in _upload_code() #L581 which is called in _handle_user_code_url() #L554, which in turn is referenced in _include_code_in_inputs() #L496. _include_code_in_inputs() is then called by _normalize_args() #L208 . This pull request address this issue.
Added entry for kms_key under Args for all the updated methods. Fix the missing space as per the build log file and also took care of the unused parameter.
I removed the trailing whitespaces on line 590 and 591 as per build logs.
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 |
Thank you for contributing @Christian-kam! Is this a duplicate of #1992? |
@ajaykarpur yes, after I made the changes to remove the white space in the code as per the build logs, I thought it would update the original pull request. I did not realize that it create a new one. The code in this one is the latest one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Could you please add unit and integration tests?
I am not really sure, how to add those tests. Can you please assist here? |
For unit test, you can add the kms_key arg to this test - https://github.com/aws/sagemaker-python-sdk/blob/master/tests/unit/test_processing.py#L257 For integ test you can create another key for testing like this - https://github.com/aws/sagemaker-python-sdk/blob/master/tests/integ/test_processing.py#L84 |
There have been any actions for a few weeks. Closing for now. Feel free to reopen when you have the chance to add the tests. |
Added entry for kms_key under Args for all the updated methods. Fix the missing space as per the build log file and also took care of the unused parameter.
Issue #, if available:
Description of changes:
In the fix #1897 that was recently merged, the kms key is not propagated throughout all the methods that require it to upload customer code.
For example:
This PR is to addresses the issue.
Testing done:
unit test
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.