Sign inSign up

milosz08/vault-dev

By milosz08

•Updated over 1 year ago

Create KV engine, KV storage and KV secrets from environment variables.

Image
0

1.2K

milosz08/vault-dev repository overview

⁠Hashicorp Vault auto-initializer image

Vault with auto-initializer. Create KV engine, KV storage and KV secrets from environment variables. ONLY FOR DEV USAGE.

⁠Table of content

⁠Key features

  • Launching Vault server in development mode (Vault configuration and secrets are created at every startup and not persisted on hard drive).
  • By default root token is set as admin.
  • You can provided one KV engine name (by default it is dev) and assign multiple KV storages.
  • Into KV storages you can assign multiples KV secrets defined as key-value environment variable.

⁠How to use

  • standalone via docker command (with example KV secrets):
$ docker run -d \
  -p 8200:8200 \
  --cap-add IPC_LOCK \
  -e VAULT_AUTO_INIT_SERVER_PORT=<optional, by default 8200> \
  -e VAULT_AUTO_INIT_ROOT_TOKEN=<optional, by default 'admin'> \
  -e VAULT_AUTO_INIT_KV_ENGINE=<optional, by default 'dev'> \
  -e KV_STORAGE_NORMAL_0=service1 \
  -e KV_STORAGE_JSON_1=service2 \
  -e V_SECRET_TOKEN_0=SuperSecretToken0 \
  -e V_SECRET_TOKEN_0=SuperSecretToken1 \
  -e KV_VALUE_JSON_1={"V_CLUSTER_NODES":[{"ip":"localhost","port":5544,"password":"secretPassword1"}]} \
  milosz08/vault-dev:latest
  • via docker compose file (with example KV secrets):
services:
  vault-dev:
    container_name: vault-dev
    image: milosz08/vault-dev:latest
    ports:
      - '8200:8200'
    environment:
      # server config
      VAULT_AUTO_INIT_SERVER_PORT: # <optional, by default: 8200>
      VAULT_AUTO_INIT_ROOT_TOKEN: # <optional, by default: 'admin'>
      VAULT_AUTO_INIT_KV_ENGINE: # <optional, by default: 'dev'>
      # kv storages
      KV_STORAGE_NORMAL_0: service1
      KV_STORAGE_JSON_1: service2
      # json combined secrets
      KV_VALUE_JSON_1: |
        {
          "V_CLUSTER_NODES": [
            { "ip": "localhost", "port": 5544, "password": "secretPassword1" },
            { "ip": "example.net", "port": 443, "password": "${PASSWORD_FROM_ENV_VARIABLE}" }
          ]
        }
      # kv secrets
      V_SECRET_TOKEN_0: SuperSecretToken0
      V_ANOTHER_SECRET_TOKEN_0: ${TOKEN_FROM_ENV_VARIABLE}
    cap_add:
      - IPC_LOCK
    networks:
      - my-infra-network

# other containers...

networks:
  my-infra-network:
    driver: bridge
⁠How define new KV storages and secrets?

  • Every KV storage variable key must be defined as KV_STORAGE_[T]_[X], where [T] is the storage type (NORMAL or JSON) [X] is the storage identifier (as number).

  • Every KV secret variable key must be defined as V_[Y]_[X], where [X] is the KV storage identifier and [Y] is the KV secret key identifier.

  • Every combined JSON secrets must be defined as KV_VALUE_JSON_[X], where [X] is the storage identifier (as number).

  • Per one KV storage you could apply ONLY ONE JSON object (JSON value must be an object not an array).

Important

Prefix `V_` is also included into KV secret identifier.

⁠Todo

  • Add the ability to insert JSON values.
  • Add the ability to create multiple KV engines.

⁠Author

Image wrapper created by Miłosz Gilga.
Original Vault image created by Hashicorp Vault⁠.
If you have any questions about this software send message: [email protected]⁠.

⁠License

This software is on GNU-GPL 3.0 license.

Tag summary

Content type

Image

Digest

sha256:0747cf719…

Size

173.2 MB

Last updated

over 1 year ago

docker pull milosz08/vault-dev