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

serverless-conditional-deployment

v1.0.10

Published

serverless plugin for environment based lambda deployment

Downloads

280

Readme

Serverless Condition Plugin

This plugin allows you to conditionally enable or disable functions based on the current stage.

Installation

npm install serverless-conditional-deployment --save-dev

Usage

To use the plugin, add the following section to your serverless.yml file:

service: service-a

provider:
  name: aws
  runtime: nodejs16.x
  memorySize: 256
  timeout: 30
  region: us-east-1
  stage: ${opt:stage, 'dev'}

plugins:
  - serverless-conditional-deployment

functions:
  function-a:
    handler: index.handlerA
    deployment:
      - 'dev'
    events:
      - http:
          path: /functiona
          method: GET
  function-b:
    handler: index.handlerB
    deployment:
      - 'stg'
    events:
      - http:
          path: /functionb
          method: GET
  function-c:
    handler: index.handlerC
    deployment:
      - 'dev'
      - 'stg'
    events:
      - http:
          path: /functionc
          method: GET

The functions section defines each function with a deployment property. If a function does not have a deployment property, it will be deployed regardless of the current stage.

deployment variable can be any string as long as its valid stage in below command -

serverless deploy --stage={deployment}

At the time of deployment, if stage is dev the serverless will deploy all lambdas where deployment array has dev mentioned.

Note

serverless deploy --stage=dev command will deploy all Lambdas in Dev invironment where deployment include dev. In the above example, function-a and function-c will be deployed. Suppose if you change deployment value and remove dev from the list, your lambda and gateway path will be distroyed as well.

Usecase

  • Keep different stack environment-wise while maintaining single serverless yml
  • Many times only developer need to pick specific feature set but they require a lot of manual work to just push a subset of lambdas to another environment
  • This plugin is basically promoting the lambdas to environment you would choose.
  • Plugin will not act on all those lambdas where deployment is not mentioned. They are bascially untouched and will be deployed to your environment

Running Tests

To run the tests, you first need to install the necessary dependencies by running the following command in the root directory of your project:

npm install

Once the dependencies are installed, you can run the tests by running the following command:

npm test

This will run the test suite using Mocha, a popular test framework for Node.js. The test results will be displayed in the console output. If any tests fail, you'll see an error message indicating which test failed and why.

Note that you can customize the test command and options in the package.json file. For example, you can change the test command to use a different test framework or specify additional options for Mocha