This repo contains a Vagrantfile mock of a Vault server demonstrating the use of consul-template & envconsul used to set environmental variables and populate placeholders within configuration files using values retrieved from vault.
The concepts herein are drawn from the Vault Direct Application Integration guide.
consul-template is tool that populates input files with values retried from either Vault or Consul; envconsul similarly sets environment variables using values retried from either Vault or Consul.
A vault server (hostname: vault-dev - in dev mode) instance is minimally configured with key-value (kv) secrets engine (kv2) enabled at the path of 'kv/'.
Example values are written to a few below and then retrieved after for passing to vault_example_app.sh via envconsul and populating vault_example_file.sh via consul-template.
Ensure that you have a setup with Virtualbox, Virtualbox Guest Additions & Vagrant already working and with sufficient hardware resources (RAM, CPU, Network)
Refer to the contents of Vagrantfile for provisioning steps.
# // Your localhost:
vagrant up ;
# // ... output of provisioning steps.
vagrant global-status ; # should show running nodes
# id name provider state directory
# -------------------------------------------------------------------------------
# 2147692 vault-dev virtualbox running /home/auser/hashicorp.vagrant_vault_envconsul_consul-template
# // SSH to vault1:
vagrant ssh vault-dev ;
# // ...
vagrant@vault-dev:~$ \
./vault_run_examples.sh ;
# ...
# // envconsul invoking vault_example.sh inline after retrieved values & then
# // consul-template is invoked to generate vault_example_file.sh thats then executed.
# when done remove eg: vagrant destroy -f vault-dev && vagrant box remove -f debian/buster64 ;This is intended as a mere practise / training.
See also: