From e03a1a84ebfe2f91077d5810aac929c69a673b91 Mon Sep 17 00:00:00 2001 From: suraj-simha Date: Wed, 3 Dec 2025 21:22:03 +0530 Subject: [PATCH] updated delete destination with force_delete parameter --- .../v1.21.x (rc)/content/api-docs/system/secrets-sync.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/vault/v1.21.x (rc)/content/api-docs/system/secrets-sync.mdx b/content/vault/v1.21.x (rc)/content/api-docs/system/secrets-sync.mdx index 40a1a01e44..f3b4130600 100644 --- a/content/vault/v1.21.x (rc)/content/api-docs/system/secrets-sync.mdx +++ b/content/vault/v1.21.x (rc)/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