Chris Olszewski
Chris Olszewski
Currently if you use #extract, the extracted files go to wherever the ruby process was started. This is an issue if the script is part of a crontab or such....
The corepack step as it exists causes issues if a machine already has corepack enabled and is using the npm shim: ``` olszewski@chriss-mbp cli % make corepack npm install -g...
I have a project with 12 functions and I get a `TooManyRequestsException: Rate exceeded` on a bunch of the Lambda API calls. Easy fix is to turn down the concurrency...
@kishinmanglani brought this up, not sure how much change this would require. Using `buildCommand` should handle most things. Might be worthwhile
Right now we update function versions/aliases on all deploys. If code, environment, and config doesn't change we don't need to publish a new version for the function.
If we create sha of the zip we could update code by parsing the `CodeSha256` and convert it from `base641` to `hex` and then create the key from that. This...
**General idea** Provide an easy way to revert an alias to a previous version and effectively "undo" a deploy **Implementation** When enabled the user can specify in their config how...
Would allow for #212 to go through and is supported runtime env for [lambda](http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html)
When trying to use shep as a library, one needs the current working directory of the node process. This can lead to some really clumsy directory changing. Suggested solution: `shep.pathPrefix...
I think we're pretty close to this being a thing. Just a matter of making sure all the functions return something/can be used without their respective commands being run first.