npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lambda-updater

v1.3.3

Published

A CLI tool to update one or more Lambda functions from a CloudFormation template.

Downloads

13

Readme

lambda-updater

A small CLI tool to update one or more AWS Lambda functions from a AWS CloudFormation template that share the same code artifact.

This is useful if you have a huge CloudFormation stack with multiple Lambda functions using the same code artifact but you don't want to re-deploy the whole stack just because you've added one line in a Lambda function. Use this to quickly upload a new version of your function's code.

Notes

  • Before you use lambda-updater, make sure that your AWS CLI is installed and configured.
  • Before you use lambda-updater, make sure that your CloudFormation stack exists, i.e. you've successfully deployed it at least once.

Install

npm

npm install -g lambda-updater

yarn

yarn global add lambda-updater

Example

lambda-updater \
    --cfn cfn.yml \
    --stack java-starter \
    --target target/target.jar \
    --functionName JavaExampleFunction \
    --useS3 shesse-lambdas

Usage

After that, just use the following command and all Java or NodeJS functions from your CloudFormation template get updated:

lambda-updater
   --cfn path
   --stack stack-name
   --target jsOrJarFile
   [--functionName name]
   [--useS3 bucketName]
   [--debug]

--cfn the relative path to your CloudFormation template

--stack the stack name for your CloudFormation template

--target a path to the JS or JAR file containing all your function code; just the functions matching the target type will be updated (might be useful if you're using Java and NodeJS functions in one project)

--functionName optional: if you just want to update one single function, provide the logical function name (= resource id in your CloudFormation template)

--useS3 optional: pass a bucket name and your target file will be uploaded to S3 first. This is useful and faster if your artifact file is quite large for a Lambda function (> 10MB). Target file will be uploaded to [LAMBDA_BUCKET]/_lambda-updater/[FILENAME]. Please consider the limitations on this approach.

--debug optional: prints out some further debug logs.

Note

The logical function name is what you define in your CloudFormation template. Example:

AWSTemplateFormatVersion: '2010-09-09'

Resources:
  YourLogicalFunctionName:
    Type: AWS::Serverless::Function
    Properties:
      # ...

If you have a function defined in your template which hasn't been deployed yet, it will be ignored and of course not updated. In this case there might be a different amount of functions in the logs which have been found and which actually have been updated.

Author

Sebastian Hesse

License

MIT License

Copyright (c) 2017 Sebastian Hesse

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.