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 🙏

© 2025 – Pkg Stats / Ryan Hefner

azure-vault-secrets

v0.0.6

Published

Package responsible for fetching the azure vault secrets

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

amittksharmaamittksharma

Keywords

Readme

azure-vault-secrets

Introduction

This module "azure-vault-secrets" will enhance the developer experience working with Azure Key Vault. This module will fetch secrets from the azure key vault and create a environment (.env) file.

In order to use this module, there are few pre-requisites that must be observed on the development/deployment machines

Pre-requisites

Features

  • Enhance developer experience
  • Minimum mandatory input from the user
  • The existing .env file will not be overridden
  • Secret keys should be present in yaml format, in "values.yaml" file
  • An environment file (.env) file will be created for the secret values

Parameters

Only a minimal set of input is required by the module to complete it's task effectively and efficiently. The module also provides hints and will work with default values in case optional parameters are not provided.

| S.No | Parameter Name | Input | Default Value | Description | | ---- | --------------- | --------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. | Vault Name | Mandatory | - | Name of the azure key vault from where secrets will be fetched | | 2. | Source Location | Optional | Project toot directory | It is the location of the yaml file that contains the secret keys. If the location is not provided the module will look for "values.yaml" file in project root directory. Note: The secret keys must be present in the file name "values.yaml" | | 3. | Target Location | Optional | Project toot directory | It is the location of .env file creation, if location is not provided the file will be created in the root directory| | 4. | Object Name | Optional | serviceConfig| This is the top object under which other secret keys are present |

Configuration

  • The package also works with a configuration file 'azureVault.yaml'
  • Package will ask user confirmation, if provided the configuration file will be created in the root directory
  • If the configuration file is present no questions will be asked

License

MIT