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

wizetorus

v1.4.0

Published

Project to save, retrieve and populate environment variables using vault server

Downloads

22

Readme

Wizetorus

Project to set, retrieve and populate environment variables using a Vault Server For the moment, this project only works with the version 2 of the KV engine API.

How to use it

  1. Install wizetorus globally

     $ npm install -g wizetorus
  2. Inside your project, create a file called .wizetorus.json with the following information:

     {
       "endpoint": "https://localhost:8200",
       "engine": "kv2",
       "project": "org/myProject"
       "environment": "develop"
     }

The full path to the secret file inside the vault server will correspond to endpoint/engine/project/<environment>. The environment attribute is optional and you can define it as a path. If you want to retrieve variables for other environment you can use the -e flag, for example wizetorus view -e devManuel. You can use environment variables previously defined inside the .wizetorus file, using the syntax <%= env('ENV_VAR') %> where ENV_VAR is the name of the variable. For example:

    {
      "endpoint": "<%= env('VAULT_ENDPOINT') %>",
      "engine": "kv2",
      "project": "org/myProject"
      "environment": "<%= env('STAGE') %>"
    }
  1. Login into the VaultServer to return the vaultToken:

     $ wizetorus login -m userpass -u username
  2. Copy the client_token attribute returned by the previous command.

  3. Export the following environment variable:

     $ export VAULT_TOKEN=client_token

If you do not want to export this variable, you can define it in the .wizetorus file under the vaultToken attribute.

  1. To set a new environment variable run:

     $ wizetorus set key=value

You can also pass a path to a valid json file:

    $ wizetorus set ./vars.json
  1. To see the environment variables run:

     $ wizetorus view
  2. See all the options for wizetorus:

     $wizetorus --help