{"id":906,"date":"2016-06-21T19:43:46","date_gmt":"2016-06-21T19:43:46","guid":{"rendered":"https:\/\/www.starkandwayne.com\/\/standing-up-vault-using-genesis\/"},"modified":"2021-09-30T11:49:14","modified_gmt":"2021-09-30T15:49:14","slug":"standing-up-vault-using-genesis","status":"publish","type":"post","link":"https:\/\/www.starkandwayne.com\/blog\/standing-up-vault-using-genesis\/","title":{"rendered":"Standing up Vault using Genesis"},"content":{"rendered":"
A few of our recent posts related to standing up BOSH deployments using Genesis<\/a> have all revolved around needing Vault<\/a> to store your credentials safely. The vault-boshrelease<\/a> makes this fairly straightforward, but there’s now a Genesis Vault template<\/a> to make running Vault even easier!<\/p>\n The procedure is similar to the other Genesis deployments:<\/p>\n$ genesis new deployment --template vault\n$ cd vault-deployments\n$ genesis new site --template bosh-lite macbook\n$ git add macbook; git commit -m "Added macbook site"\n$ bosh target bosh-lite\n$ genesis new env macbook sandbox\n$ cd macbook\/sandbox\n$ make deploy\n$ git add .; git commit -m "Added initial sandbox environment"\n# lather, rinse, repeat as needed for all of your sites\/environments\n<\/code><\/pre>\n