Add '-x' / '--excludeGlobs' args for general file exclusion on deploy.#48
Add '-x' / '--excludeGlobs' args for general file exclusion on deploy.#48rafalyesware wants to merge 5 commits intomotdotla:masterfrom rafalyesware:rkb-add-exclude-support
Conversation
This lets me e.g. exclude not only `.env` but by `.env.prod` / `.env.dev` and any other junky / sample files that happen to live in the method's directory. Or for that matter to move all those files into a sub- directory and exclude that. Less policy, more flexibility.
This excludes some of the files created by `node-lambda setup`, which while handy for development, aren't at all needed as part of the data uploaded to AWS Lambda.
|
Thanks for this @rafalyesware. I'll take a look this weekend. |
|
Been a few weeks since that weekend; merged up to current master in case it helps @motdotla |
|
@rafalyesware if we can get https://github.com/rafalyesware/node-lambda/issues/1 merged into your branch, I'd like to get this merged here! Adds great functionality. |
|
Thanks, I'll see what I can do this weekend. --rafal
|
|
As a general point, #40 already wanted to use |
|
@rafalyesware did you get a chance to take a look already? I have been keeping the PR up to date with the changes to master. |
|
Deprecated by: #80 |
This lets me e.g. exclude not only
.envbut by.env.prod/.env.devand any other junky / sample files that happen to live in the method's
directory. Or for that matter to move all those files into a sub-
directory and exclude that. Less policy, more flexibility.
Fixes #44 and fixes #32