Skip to content

Latest commit

 

History

History
44 lines (28 loc) · 1.58 KB

README.md

File metadata and controls

44 lines (28 loc) · 1.58 KB
Raw

vault-traverser

Walk a given Vault path to check if a secret exists in the given path.

Testing Release

Installation

brew tap lucassha/homebrew
brew install lucassha/homebrew/traverse

Testing

A Makefile hosts the necessary components to spin up a test Vault server in Docker and automatically write some secrets into it for testing traverse.

Spin up a test server: make spinup. This creates a Vault Dev server from the base Docker image and writes some sample secrets into the default Vault path /secret.

Usage

Traverse Usage Example

Each user's authentication to Vault may differ, so YMMV on utilizing traverse to authenticate to Vault. env | grep -i vault_ can be provide what Vault variables are set in the shell. All Vault Env Vars listed here.

Examples

# search the path /secret for the AWS key AKIA-12345678
traverse --path secret --secret AKIA-12345678

# search the path /secret for the AWS key AKIA-12345678. /secret is the default path
traverse --secret AKIA-12345678

# search the path /containers/production for the secret test_key
traverse --path containers/production --secret test_key

TODO

  • Add testing for SearchPath method in Vault package
  • Fully test kv v1
  • Add concurrent searching for multiple paths