c8volt ops purge all-process-definitions

Purpose

Deleting process definitions is not just resource cleanup. c8volt ops purge all-process-definitions discovers candidate versions, plans process-instance impact, blocks active impact unless forced, then deletes selected definitions with an audit report.

In Action

c8volt ops purge all-process-definitions demo

Use When

  • process-definition versions should be removed after impact planning
  • active process-instance impact must be visible before mutation
  • Camunda 8.9+ deletion behavior should be driven by one audited workflow

Basic Usage 

c8volt ops purge all-process-definitions --bpmn-process-id <bpmn-process-id> --latest --dry-run

Generated reference: ops purge all-process-definitions.

Best Variants 

c8volt ops purge all-process-definitions --key <process-definition-key> --force --report-file process-definition-purge.md
c8volt ops purge all-process-definitions --bpmn-process-id <bpmn-process-id> --latest --force --report-file process-definition-purge.md

Built From Lower-Level Commands 

c8volt get process-definition --bpmn-process-id <bpmn-process-id>
c8volt delete process-definition --key <process-definition-key>

Generated references: get process-definition, delete process-definition.

Safety

--dry-run reports selected definitions and process-instance impact without mutation. Real execution requires confirmation unless automation controls are used. Full process-definition purge is supported from Camunda 8.9 onward.

A named tenant limits discovery. An empty tenant or --all-tenants searches across tenants visible to the authenticated identity. --all-tenants conflicts with an explicit --tenant value. Explicit keys use backend authorization without tenant filtering.

Forced Cleanup

With --force, cleanup cancels root process instances, waits for active instances to drain, deletes process-instance histories, and then deletes process definitions.