From 48da554763f4f2bfa72ee6f2e1f4853b07f3294a Mon Sep 17 00:00:00 2001 From: "Colton J. McCurdy" Date: Wed, 13 Nov 2019 02:59:29 -0500 Subject: [PATCH] docs/website: fix broken chef-puppet with vault blog link (#7850) Signed-off-by: Colton McCurdy --- website/source/docs/vs/chef-puppet-etc.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/vs/chef-puppet-etc.html.md b/website/source/docs/vs/chef-puppet-etc.html.md index a0f6b0611d..074cc54534 100644 --- a/website/source/docs/vs/chef-puppet-etc.html.md +++ b/website/source/docs/vs/chef-puppet-etc.html.md @@ -46,6 +46,6 @@ accessed. It is rare to have a single key that can access all secrets. This makes it easier to have fine-grained access for consumers of Vault. For tips on how to integrate Vault using configuration management, please see -[Using HashiCorp's Vault with Chef](https://www.hashicorp.com/blog/using-hashicorps-vault-with-chef.html). +[Using HashiCorp's Vault with Chef](https://www.hashicorp.com/blog/using-hashicorps-vault-with-chef/). Although this post is about Chef, the principles can be broadly applied to many of the tools listed here.