From e71b6fde39f00e094ffdc13ca21b1b0f81621c8c Mon Sep 17 00:00:00 2001 From: Joonas Bergius Date: Thu, 26 Sep 2024 14:18:47 -0500 Subject: [PATCH] chore: fix secrets page formatting Signed-off-by: Joonas Bergius --- docs/deployment/security/secrets.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/deployment/security/secrets.mdx b/docs/deployment/security/secrets.mdx index 611cbd29..cea4750c 100644 --- a/docs/deployment/security/secrets.mdx +++ b/docs/deployment/security/secrets.mdx @@ -96,6 +96,7 @@ This payload is encrypted using the xkey provided in the `Wasmcloud-Host-Xkey` h // Omitted on success "error": "" } +``` A successful response will only contain the secret payload. An unsuccessful response should contain an error key with a string message describing the error. Examples of what might cause such an error include: @@ -108,7 +109,7 @@ Secrets backend implementations may also have additional API endpoints as needed ### Secret stores -All wasmCloud stores are secret references which are pieces of config that start with `secret_` and have the following structure: +All wasmCloud stores are secret references which are pieces of config that start with `SECRET_` and have the following structure: ```rust #[derive(Debug, Serialize, Deserialize, Clone, PartialEq, Eq, Hash)]