From 42443518f401da0b59016277f5b11cb144519db3 Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Mon, 8 Dec 2025 18:42:56 +0530 Subject: [PATCH 1/5] added force-delete parameter to delete destination in secret sync --- .../vault/v1.16.x/content/api-docs/system/secrets-sync.mdx | 4 ++++ .../vault/v1.19.x/content/api-docs/system/secrets-sync.mdx | 4 ++++ .../vault/v1.20.x/content/api-docs/system/secrets-sync.mdx | 4 ++++ .../vault/v1.21.x/content/api-docs/system/secrets-sync.mdx | 4 ++++ 4 files changed, 16 insertions(+) diff --git a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx index 4827785d87..bdab40c391 100644 --- a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx @@ -221,6 +221,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. +- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. +This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and +will require manual cleanup. + ### Sample request ```shell-session diff --git a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx index f50aa72fc4..57315f65b6 100644 --- a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx @@ -223,6 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. +- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. +This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and +will require manual cleanup. + ### Sample request ```shell-session diff --git a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx index d1a2183fa3..fb17d09e67 100644 --- a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx @@ -223,6 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. +- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. +This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and +will require manual cleanup. + ### Sample request ```shell-session diff --git a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx index 40a1a01e44..f3b4130600 100644 --- a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx @@ -223,6 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. +- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. +This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and +will require manual cleanup. + ### Sample request ```shell-session From 60341b372f40d949edca1b851da0f2eadc1abb8a Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Wed, 10 Dec 2025 08:55:50 +0530 Subject: [PATCH 2/5] Update content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- .../vault/v1.16.x/content/api-docs/system/secrets-sync.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx index bdab40c391..826a52bf4a 100644 --- a/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.16.x/content/api-docs/system/secrets-sync.mdx @@ -221,9 +221,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. -- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. -This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and -will require manual cleanup. +- `force_delete` `(bool: false)` - When true, Vault deletes a destination even + if its associations cannot be unsynced. Only use `force-delete` as a + last-resort deletion mechanism as it orphans any secrets already synced to the + external provider, which requires manual cleanup. ### Sample request From 2e128dce9b885fa754300082e0ffa9daeb39151c Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Wed, 10 Dec 2025 08:55:56 +0530 Subject: [PATCH 3/5] Update content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- .../vault/v1.19.x/content/api-docs/system/secrets-sync.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx index 57315f65b6..d604751c3b 100644 --- a/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.19.x/content/api-docs/system/secrets-sync.mdx @@ -223,9 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. -- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. -This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and -will require manual cleanup. +- `force_delete` `(bool: false)` - When true, Vault deletes a destination even + if its associations cannot be unsynced. Only use `force-delete` as a + last-resort deletion mechanism as it orphans any secrets already synced to the + external provider, which requires manual cleanup. ### Sample request From 1069a4488e167915428098ee7d7feb8e8fe3f2fd Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Wed, 10 Dec 2025 08:56:05 +0530 Subject: [PATCH 4/5] Update content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- .../vault/v1.20.x/content/api-docs/system/secrets-sync.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx index fb17d09e67..06fcd5a7bc 100644 --- a/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.20.x/content/api-docs/system/secrets-sync.mdx @@ -223,9 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. -- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. -This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and -will require manual cleanup. +- `force_delete` `(bool: false)` - When true, Vault deletes a destination even + if its associations cannot be unsynced. Only use `force-delete` as a + last-resort deletion mechanism as it orphans any secrets already synced to the + external provider, which requires manual cleanup. ### Sample request From db934d17e2dc96f0278ddcd3700dc847a57b090f Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Wed, 10 Dec 2025 08:56:14 +0530 Subject: [PATCH 5/5] Update content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- .../vault/v1.21.x/content/api-docs/system/secrets-sync.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx index f3b4130600..55f34e1f88 100644 --- a/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.21.x/content/api-docs/system/secrets-sync.mdx @@ -223,9 +223,10 @@ associations cannot be deleted unless they are also purged. - `purge` `(bool: false)` - If true, asynchronously unsync all secrets and delete all associations managed by this destination before it is deleted. -- `force_delete` `(bool: false)` - If true, deletes a destination even if its associations cannot be unsynced. -This should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and -will require manual cleanup. +- `force_delete` `(bool: false)` - When true, Vault deletes a destination even + if its associations cannot be unsynced. Only use `force-delete` as a + last-resort deletion mechanism as it orphans any secrets already synced to the + external provider, which requires manual cleanup. ### Sample request