Click commands should use correct keyword args for requirements #83

karthich · 2017-12-05T19:42:59Z

The build command in scripts/lambda uses keyword arguments that are inconsistent with the build function in aws_lambda.py
def build(use_requirements, local_package, config_file): aws_lambda.build( CURRENT_DIR, use_requirements=use_requirements, local_package=local_package, config_file=config_file, )
aws_lambda build function signature looks like this:
def build( src, requirements=False, local_package=None, config_file='config.yaml'):

The text was updated successfully, but these errors were encountered:

karthich · 2017-12-05T19:47:21Z

Looks like build, deploy, deploy s3 all seem to be using use_requirements key word args. Maybe the aws_lambda function needs to be edited to accomodate these variable name changes?

…requirements

Issue: #83

karthich changed the title ~~Build command should use correct keyword args for requirements~~ Click commands should use correct keyword args for requirements Dec 5, 2017

karthich pushed a commit to karthich/python-lambda that referenced this issue Dec 5, 2017

Issue: nficano#83 Click commands should use correct keyword args for …

4f215c9

…requirements

franciscohanna92 mentioned this issue Jan 6, 2018

Error when using 'lambda deploy_s3': Unexpected keyword argument 'use_requirements' #89

Open

nficano / python-lambda

Click commands should use correct keyword args for requirements #83

Click commands should use correct keyword args for requirements #83

karthich commented Dec 5, 2017 •

edited

karthich commented Dec 5, 2017

nficano / python-lambda

Click commands should use correct keyword args for requirements #83

Click commands should use correct keyword args for requirements #83

Comments

karthich commented Dec 5, 2017 • edited

karthich commented Dec 5, 2017

karthich commented Dec 5, 2017 •

edited