Skip to content

Conversation

@asaolabs
Copy link
Contributor

This is related to issue #64 not working as expected. Added the capability to copy source directories into the zip package in the build process. To control which folders are copied (as there may be additional folders that shouldn't be deployed within the project structure), there is a new build configuration section in the config.yaml file that includes a new property "source_directories".

Note: This makes it much easier to build a lambda function that talks to Redshift/Postgres databases using the precompiled psycopg2.

…ge".

Added the ability to explicitly define the list of "source" subdirectories in the config.yaml file under a new "build" configuration section.  Decided it was perhaps best to allow explicit declaration of the folder list so we don't build undesirable (.git) folders into the zipfile.  Modified the template config.yaml with this setting as well.
…ge".

Added the ability to explicitly define the list of "source" subdirectories in the config.yaml file under a new "build" configuration section.  Decided it was perhaps best to allow explicit declaration of the folder list so we don't build undesirable (.git) folders into the zipfile.  Modified the template config.yaml with this setting as well.
…en't set for the build, build/source_directories properties. We now handle these cases correctly and default to the existing behavior if the values are missing.
…t a function exists wasn't calling multiple times if you have more than 50 lambda functions configured. For those users who have lots of functions defined, the deploy will try to re-create an existing lambda function
@nficano nficano merged commit 3c677aa into nficano:master Sep 18, 2017
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