gfc-collective / sbt-aws-lambda

15%

master: 20%

push

github

Add deployLambdaInWaves task (#224)

Adds a new sbt task, deployLambdaInWaves, that mirrors deployLambda but
splits handlers into waves of doubling size (1, 2, 4, 8, …) and deploys
handlers within the same wave in parallel. Existing deployLambda behavior
is unchanged.

Motivation: when a single sbt-aws-lambda project owns many handlers (e.g.
19 in flowcommerce/dynamodb-adapter-lambdas), the existing serial
publishVersion loop both (a) takes a long time and (b) on partial failure
leaves the remaining handlers stuck on the previous release. A leading
canary wave of 1 exposes failures before the whole fleet is touched, and
parallelism within each wave shortens the total deploy.

The helper splitIntoWaves is exposed as package-private so its shape can
be asserted directly from utest without spinning up AWS clients. The
deploy step itself reuses the existing per-handler updateFunctionCode
path; the only difference is that the calls are wrapped in Futures and
awaited per wave on ExecutionContext.global.

Also bumps version to 1.4.0.

7 of 42 new or added lines in 1 file covered. (16.67%)

54 of 367 relevant lines covered (14.71%)

0.74 hits per line