-
Notifications
You must be signed in to change notification settings - Fork 7
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
Have Default Action be Single Upload of the Current Directory #2
Comments
I made a PR, for the most basic of handling this. I'll need to dig in a bit more and see about the other stuff. |
This changes how we do things, pursuant to #2, to only upload a single Lambda dir at a time, either the CWD or whatever is specified by `-d`. We try to take care to be careful not to upload .env files. I've added an example for how to upload multiple Lambdas in a CI environment.
I created PR #4 to address some of the issues that we discussed - I'm going to play with it a bit over the next day or two but it seems to work correctly. Feel free to give it a gander and test it out and if you have any issues/ideas feel free to let me know. I'l merge it in a couple days if I don't find anything. |
This changes how we do things, pursuant to #2, to only upload a single Lambda dir at a time, either the CWD or whatever is specified by `-d`. We try to take care to be careful not to upload .env files. I've added an example for how to upload multiple Lambdas in a CI environment.
Resolved by #4 |
As requested in issue #1, it might make more sense that the default deploy action is to deploy the current directory as a single Lambda, and only search for multiple Lambdas if the
-d
option is given. Some things to consider:The text was updated successfully, but these errors were encountered: