From ec79756e2b2a7b6b8f49f849c5ac9412676816c3 Mon Sep 17 00:00:00 2001 From: Crossplane Date: Thu, 1 Dec 2022 21:47:53 +0000 Subject: [PATCH] docs snapshot for crossplane version `v1.10` --- content/v1.10/guides/vault-as-secret-store.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v1.10/guides/vault-as-secret-store.md b/content/v1.10/guides/vault-as-secret-store.md index e0c7962f..a69efad2 100644 --- a/content/v1.10/guides/vault-as-secret-store.md +++ b/content/v1.10/guides/vault-as-secret-store.md @@ -26,7 +26,7 @@ which expect input parameters that could be sensitive. Initial password of a managed database is a good example of this category. It is already possible to use Vault for the 1st category (i.e. Provider -Credentials) as described in [the previous guide]. 3rd use case is a relatively +Credentials) as described in [the previous guide]. The 3rd use case is relatively rare and being tracked with [this issue]. In this guide we will focus on the 2nd category, which is storing Connection