README.md
Heroku-like experience with AWS Lambdas.
Features
Connecting current directory with lambda (like heroku git:remote)
$ lambdoku init
this allows you to omit the -a param for all commands below
Simplified environment variables management (heroku config)
$ lambdoku config:set ONE=1 TWO=2
$ lambdoku config
ONE=’1′
TWO=’2′
$ lambdoku config:get ONE
ONE=’1′
Simplified releases management (heroku releases)
$ lambdoku releases
22 | Setting env variables AA | 2016-11-26T21:12:46.894+0000
21 | Unsetting env variables XY | 2016-11-26T21:10:04.302+0000
20 | Setting env variables BB,XY | 2016-11-26T20:57:57.340+0000
…
$ lambdoku rollback 18
$ lambdoku releases
23 | Rolling back to version 18 | 2016-11-26T21:35:45.952+0000
22 | Setting env variables AA | 2016-11-26T21:12:46.894+0000
21 | Unsetting env variables XY | 2016-11-26T21:10:04.302+0000
20 | Setting env variables BB,XY | 2016-11-26T20:57:57.340+0000
…
in the example both code and configuration is rolled back from version 18.
Pipelines (heroku pipelines)
(actually the main reason why lambdoku was created)
$ lambdoku init lambdaDev
$ lambdoku pipeline:add lambdaStage
$ lambdoku pipeline:add lambdaProd -a lambdaStage
$ lambdoku pipeline
lambdaStage
$ lambdoku pipeline:promote
now lambdaDev and lambdaStage have the same codebase.
lambdaStage can
