Skip to content

Added force_delete parameter to delete destination for vault secrets-sync feature #1443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
suraj-simha wants to merge 1 commit into
base: vault/1.21.x
Choose a base branch
from
Draft

Added force_delete parameter to delete destination for vault secrets-sync feature #1443

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/vault/v1.21.x (rc)/content/api-docs/system/secrets-sync.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading