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

@xplora-uk/secrets

v1.7.0

Published

shared secrets reader library

Downloads

79

Readme

secrets

use AWS SDK and read settings from Secrets Manager

It covers two scenarios:

A:

The secret my_app is already loaded into process.env e.g. in an AWS ECS container. process.env.my_app is { "DB_PASS": "secretPassword" }

Then, result.data is an object based on JSON.parse(process.env.my_app).

B:

The secret is not in process.env but only in AWS Secrets Manager.

Then, result.data is an object based on JSON.parse(secret) the secret found on AWS.

DEV

Check code inside src.

requirements for dev

  • Node v18.x

install, build, configure, test

npm i
npm run build
cp _sample.env .env
# edit it

Sample:

AWS_ACCESS_KEY_ID="key"
AWS_SECRET_ACCESS_KEY="secret"
AWS_REGION="eu-central-1"
my_app='{ "PASSWORD": "pass1234" }'
DB_HOST="${MYSQL_HOST}"

Run tests:

# check tests inside src/__tests__
npm run test
npm run test:coverage

USAGE

requirements for usage

  • Node v18.x

installation

npm i @xplora-uk/secrets

configuration

import { newSecretsReader } from '@xplora-uk/secrets';

// configure and load
const secretsReader = newSecretsReader({}); // defaults to aws
//const secretsReader = newSecretsReader({ kind: 'aws' });

// use with side-effect on process.env
const secret = await secretsReader.readSecret({ secretId: process.env.APP_ID, env: process.env, updateEnv: true });
if (secret.error) console.error('failed to read secret', secret.error);
// also, secret.data contains secret object

batch reader

Sample:

const env: IEnvSettings = {
  ...process.env, // use a copy of process.env, if you do not change it!
  PROGRAM_NAME: 'my-test-app',
};
const { errors } = await batchReadSecrets({ env }); // note side-effect on env
  1. Load _defaults.env file.
  2. Load _sharedSecrets.json, if it was injected by CI/CD script.
  3. Load shared secret from AWS, if it exists.
  4. Load _secrets.json file, if it was injected by CI/CD script.
  5. Load {env.PROGRAM_NAME} secret from AWS, if it exists.
  6. Load .env file, if it exists. Developers can copy default settings and override.
  7. Expand variables using dotenv-expand.

In each step, we will merge settings found into env object.