Skip to content

Commit e335a02

Browse files
committed
docs(purge): auto delete expired KVs
Part of kestra-io/kestra#12320
1 parent 943d34c commit e335a02

File tree

1 file changed

+14
-0
lines changed
  • src/contents/docs/10.administrator-guide/purge

1 file changed

+14
-0
lines changed

src/contents/docs/10.administrator-guide/purge/index.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,20 @@ tasks:
6464
Purge tasks permanently delete data. Always test in non-production environments first.
6565
:::
6666

67+
## Auto-delete expired Key-value pairs
68+
69+
Rather than create a system flow to regularly purge Key-value pairs, you can add a global configuration to your Kestra Configuration/Application file that auto deletes expired Key-value pairs:
70+
71+
```yaml
72+
kestra:
73+
kv:
74+
purge-expired:
75+
enabled: true # default true
76+
initial-delay: PT5S # default PT6H
77+
fixed-delay: PT5S # default PT6H
78+
batch-size: 10 # default 1000
79+
```
80+
6781
## Purge tasks vs. UI deletion
6882

6983
Purge tasks perform **hard deletion**, permanently removing records and reclaiming storage. In contrast, deleting items in the UI is a **soft deletion**—the data is hidden but retained (e.g., revision history and past executions can reappear if a flow with the same ID is recreated).

0 commit comments

Comments
 (0)