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

config-with-paramstore

v1.1.1

Published

a node module that makes it easy to create config files that reference aws paramstore with __PLACEHOLDER__s

Downloads

304

Readme

config-with-paramstore

AWS Paramstore enables you to store secrets on amazon's servers. The AWS-SDK provides a way to retreive secrets from this vault on their servers. This package uses the flat object keys of your config file to replace every __PARAM__ in your config file with the velue found in the AWS parameter store for that flat object key.

Simple Example:

config.json

{
  "parameterStoreNamespace": "my-awesome-app/",
  "database": {
    "username": "dummyuser",
    "password": "__PARAM__"
  }
}

is converted into

{
  "database": {
    "username": "dummyuser",
    "password": "some-password found at aws-paramstore:my-awesome-app/database.password"
  }
}

I.e., then the value for the key my-awesome-app/database.password is retreived from parameter store and replaces __PARAM__.

Installation

1. define the base key of your config. this enables you to group together keys per service under a unique namespace.

In your config object, define the key parameterStoreNamespace for this functionality.

e.g., if your config is:

{
  parameterStoreNamespace: 'my-app/',
  database: {
    username: 'dummyuser',
    password: '__PARAM__'
  },
}

then we would retreive the __PARAM__ value from the parameter store key my-app/database.password.

2. create keys in AWS Param Store through the AWS Console

https://console.aws.amazon.com/systems-manager/parameters?region=us-east-1

3. create your config file

e.g.,

{
  "parameterStoreNamespace": "app-name.service-name.environment",
  "database": {
    "name": "databasename",
    "host": "local",
    "port": 3306,
    "username": "some-user",
    "password" : "__PARAM__"
  }
}

Usage

example:

config:

{
  "parameterStoreNamespace": "ahbode.service-graphql.local",
  "database": {
    "name": "ahbode-graphql",
    "host": "local",
    "port": 3306,
    "username": "lambda-user",
    "password" : "__PARAM__"
  }
}

javascript:

import Config from 'config-with-paramstore';

// initialie config cache
const configInstance = new Config();

(async () => {
  // get default env config
  const config =  await configInstance.get();

  // check that it has been changed from __PARAM__
  expect(config.database.password).not.toEqual('__PARAM__');
})()

Extras

Environmental Variables

This package supoprts setting environmental variables in your config with the __ENV__ key. You can use packages like dotenv to source environmental variables from files into your env. This package will not do that for you.

You can define a namespace for envVariables, just like you can do for param store, with the config key environmentVariableNamespace. Note: environmental variables can not have periods in their names, so you must use underscores (_) instead of periods (.).