Lamb-duh

# v1 to v2 Migration

# Major Changes

  • Lambda installation, local configuration and deployment now via a CLI
    • Lamb-duh is now on NPM!
  • Complete, from-scratch rewrite of the codebase
  • Lamb-duh leverages AWS services even more to boost efficiency
  • Large deployments are considerably faster
  • Deployments are now versioned (off by default), which allows for not breaking users browser applications that may be cached.
    • S3 deployments can have the endpoint string automatically updated
    • For local testing/manual updates: following deployment the log will contain the correct endpoint, and using the SNS notification will supply it via SNS.
    • The number of saved aliases can be controlled, both as total numbers and amount of time
    • See versioningLimits in Lamb-duh configuration: API Gateway Tasks for more details and how to turn the feature off
  • Start/Completion notifications now provided (via SNS)
  • Historical storage of the compressed archive file is available, and on by default

# Breaking Changes

While v2.0.0 is a total rewrite of the codebase from scratch, every effort has been made to maintain a nearly identical JSON configuration format. Any breaking changes are below.

  1. Configuration files must be included in the triggering archive. Lamb-duh no longer supports using a default configuration.
  2. IAM Roles
    • the s3:ListBucket permission is now required for the triggering bucket where the code archive is placed to start the deployment process
    • The lambda:DeleteAlias permission is now required
  3. Lambda Tasks
    • To keep with AWS standards, function handlers now default to handler instead of the Lamb-duh v1.x required lambda. A handler property has been added to both the function definition, and the task defaults, and can now be defined for all task functions or per-function.
      • To maintain v1.x compatibility, add "handler": "lambda" as a setting for all existing Lambda task in the defaults object.
  4. API Gateway Tasks
    • It's no longer possible to operate without a stage configured. As API Gateway integration is presumably for deployment, this shouldn't impact on production usage; however, it does break for anyone who previously ran without a stage configured.
    • task.stage is now task.deployment.stage

←