Fix for handling S3 deployment arguments #94
Merged
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.
When using
deploy_s3, theupdate_functionandcreate_functionfunctions takeuse_s3as*argsands3_fileas**kwargs, which causes thes3_fileto be empty anduse_s3to equal(True, <s3_file>), which then causes the deployment to fail because theS3Keyvalue submitted to AWS is just{}.This PR fixes it so that those arguments are properly passed and deployment goes through.