Verentis

Documentation

Executions

Run files on the platform, stream logs, and inspect or cancel executions.

An execution runs a workspace file through the execution engine that handles its file type. The verentis exec command group starts and inspects them.

Run a file

verentis exec run /scripts/transform.py --follow          # run remotely, stream logs live
verentis exec run /scripts/etl.py --arg --verbose --params '{"rows":10}'
<filePath>
Required

The workspace file to execute.

--engine <engineId>

Explicit engine id. Default: resolved from the file type.

--tool <tool>

Engine tool to invoke. Default: the engine's default tool (e.g. execute).

--mode <mode>

request-response or long-running.

--arg <value...>

Command-line arguments passed to the script. Repeatable.

--params <json>

Tool parameters JSON (engine.context.input.parameters).

--follow

Wait for completion and stream logs.

Inspect, stream and cancel

verentis exec list --workspace <id>              # --file to filter by path; paged
verentis exec get <executionId>
verentis exec logs <executionId> --follow        # live SSE log streaming
verentis exec cancel <executionId>

Iterating locally?

exec run runs on the platform. To iterate on a script from your machine against real workspace files — with a debugger — use the developer loop instead.

Next

See which engines exist and which handles a file type in Engines.