Skip to content
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

Optionally use code from S3 rather than zip - Fixes #65 #68

Closed
wants to merge 3 commits into from

Conversation

coopernurse
Copy link
Contributor

This adds support for an optional 'code' block inside the 'lambda'
config that specifies the s3 bucket/key/version to use when creating or
updating the lambda function.

If the 'code' block is provided, no zip file is created.

I also added a section to the README that explains how to use this.

This adds support for an optional 'code' block inside the 'lambda'
config that specifies the s3 bucket/key/version to use when creating or
updating the lambda function.

If the 'code' block is provided, no zip file is created.
key: path/to/hello.jar
# version is optional and refers to the object's version ID
# see: http://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectVersioning.html
version: 123
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when this is omitted? What happens when we migrate from non-code from s3 to code from s3?

@josegonzalez
Copy link
Contributor

Needs tests :)

@josegonzalez
Copy link
Contributor

bump

@josegonzalez
Copy link
Contributor

Closing as the OP never responded :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants