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

Bundling too many artifacts #183

Open
opobla opened this issue Aug 20, 2019 · 4 comments
Open

Bundling too many artifacts #183

opobla opened this issue Aug 20, 2019 · 4 comments

Comments

@opobla
Copy link

opobla commented Aug 20, 2019

Hi!
When doing lambda deploy too many artifacts get bundled:

Bundling: 'README.md'
Bundling: 'service.py'
Bundling: 'requirements.txt'
Bundling: 'event.json'
Bundling: '.gitignore'

Is there a way to exclude/include explicitly what should be bundled?
Regards

@marcelorcorrea
Copy link

marcelorcorrea commented Aug 21, 2019

It does't answer your question completely, but if you need to include some source folder, you can add it in your config.yaml in build > source_directories separated by comma.

@opobla
Copy link
Author

opobla commented Aug 22, 2019

I have tried to put the source code in a lib folder y include it in the config.yaml, but the result is that invoke no longer works and build bundles everything in the root folder and also the contents of the lib folder.

I think that the idea should be to add support for a sort of .lambdaignore mechanism to avoid bundling artifacts that do not belong to the execution environment of the lambda function.

@unrealsolver
Copy link

@opobla, indeed there are no possibility to this. According to the source code, the tool packs whatever content of the directories. I going to came up with PR addressing this issue sooner or later.

@Alan-Penkar-QB
Copy link

I would benefit from this functionality as well

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

No branches or pull requests

5 participants