From 59f583ff7c145611de385d7aca5be0c6d27db462 Mon Sep 17 00:00:00 2001 From: Gabor Szarnyas Date: Thu, 29 Feb 2024 21:14:51 +0100 Subject: [PATCH] Fix URLs --- docs/configuration/secrets_manager.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuration/secrets_manager.md b/docs/configuration/secrets_manager.md index 11b528869c3..13bad2776e0 100644 --- a/docs/configuration/secrets_manager.md +++ b/docs/configuration/secrets_manager.md @@ -24,7 +24,7 @@ For each type, there are one or more "secret providers" that specify how the sec ### Creating a Secret -Secrets can be created using the [`CREATE SECRET` SQL statement](sql/statements/create_secret). +Secrets can be created using the [`CREATE SECRET` SQL statement](../sql/statements/create_secret). Secrets can be **temporary** or **persistent**. Temporary secrets are used by default – and are stored in-memory for the life span of the DuckDB instance similar to how settings worked previously. Persistent secrets are stored in **unencrypted binary format** in the `~/.duckdb/stored_secrets` directory. On startup of DuckDB, persistent secrets are read from this directory and automatically loaded. #### Secret Providers @@ -62,7 +62,7 @@ This will write the secret (unencrypted) to the `~/.duckdb/stored_secrets` direc ### Deleting Secrets -Secrets can be deleted using the [`DROP SECRET` statement](sql/statements/create_secret#syntax-for-drop-secret), e.g.: +Secrets can be deleted using the [`DROP SECRET` statement](../sql/statements/create_secret#syntax-for-drop-secret), e.g.: ```sql DROP PERSISTENT SECRET my_persistent_secret;