c8volt ops execute smoke-test

Purpose

A profile can look valid and still fail at the first real operational step. c8volt ops execute smoke-test proves the configured environment by connecting, deploying a c8volt-owned fixture, starting process instances, walking them, and cleaning up.

In Action

c8volt ops execute smoke-test demo

Use When

  • a profile should be verified end to end
  • deployment, runtime, traversal, and cleanup should be tested together
  • CI or operators need a report that the profile passed

Basic Usage 

c8volt ops execute smoke-test --dry-run

Generated reference: ops execute smoke-test.

Best Variants 

c8volt ops execute smoke-test --report-file smoke-test.md
c8volt ops execute smoke-test --no-cleanup --report-file smoke-test.md

Built From Lower-Level Commands 

c8volt config test-connection
c8volt run process-instance --bpmn-process-id <bpmn-process-id>
c8volt walk process-instance --key <created-process-instance-key>

Generated references: config test-connection, run process-instance, walk process-instance, delete process-instance.

Output And Safety

--dry-run reports the planned smoke-test steps without mutation. Real execution creates c8volt-owned runtime data and cleans it up unless --no-cleanup is supplied. On Camunda 8.8, prefer --no-cleanup because full process-definition deletion is supported by c8volt from Camunda 8.9 onward.