Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Click commands should use correct keyword args for requirements #83
Comments
|
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? |
karthich
changed the title
karthich
pushed a commit
to karthich/python-lambda
that referenced
this issue
Dec 5, 2017
nficano
added a commit
that referenced
this issue
Jan 4, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: