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

enhanced-env-azure-vault

v1.2.6

Published

Managing environment variables using Azure Key Vault tags

Downloads

10

Readme

enhanced-env-azure-vault

Managing environment variables using Azure Key Vault tags.

Problem

When your application has many environment variables, they become difficult to manage.

Sharing long env file with team members and then sharing again when updating them is a difficult task. Managing multiple environemnt (local, demo, staging, production,...) again introduces some more challenges.

Solution

If you are already using azure, manage your environment variables using key vault. It's a good service with many benefits. (learn more)

  • create a azure key vault.
  • create a service principal with access to above key vault.
  • use this package to set up and load env.

Installation

npm install enhanced-env-azure-vault

or

yarn add enhanced-env-azure-vault

Usage

Send all your environment variables to your azure key vault.

Setup process is described in /examples/insert.ts.


// enhanced-env-azure-vault expects the following environment variables
// KEY_VAULT_URI: The keyvault uri in Azure
// AZURE_TENANT_ID: The tenant ID in Azure Active Directory
// AZURE_CLIENT_ID: The application (client) ID registered in the AAD tenant
// AZURE_CLIENT_SECRET: The client secret for the registered application

import * as manager from 'enhanced-env-azure-vault';

// Your environment variables.
const envKeys = [

    { name: 'API_URL', value: 'AA', tags: { environment: 'testing', type: 'backend' } },
    { name: 'API_URL_FE', value: 'AA', tags: { environment: 'staging', type: 'frontend' } }

    // Any other variables
];

const result = await manager.setup({ envKeys });

Load Variables in your app.

import * as manager from 'enhanced-env-azure-vault';
const result = await manager.init({ envKeys });

Getting all Variables from Azure, based on tags.

const scanVault = async (): Promise<secretObject[]> => {
  return await manager.listAll();
};

scanVault()
  .then(async (res) => {
    await res.forEach((element) => {
      if (element.tags && element.tags.type === "backend") {
        console.log(element);
        getEnv(element.name).then((env) => console.log(process.env));
      }
    });
  })
  .then((env) => console.log(env))
  .catch((err) => {
    console.log("Error scanning Azure Vault: ", err);
  });

// Now we can distinguish for example [testing / staging / production] environments
// AND type: [backend / frontend]
// OR utilize any other tag patterns