Codcel can be run from the command line for automated workflows, CI/CD pipelines, and scripted code generation. The CLI accepts the same configuration options available in the desktop app.
Comma-separated list of Parquet file paths for table data input
Parquet files are self-describing, so no header or delimiter settings are needed. Multiple Parquet files can provide data for the same table using prefix naming (e.g., Sales.parquet, Sales_part1.parquet). If both Parquet and CSV files exist for the same table, the Parquet files take priority.
Control which versions of the Codcel engine dependencies are used in the generated code. For each engine you can specify either a git tag (for releases) or a git branch (for development/PR testing). If both tag and branch are specified for the same engine, the tag takes priority. If neither is specified, the generated code defaults to branch = "main".
Argument
Default
Description
--calculation-engine-tag
(empty)
Git tag for codcel-calculation-engine (e.g. release-0.1.5)
--calculation-engine-branch
(empty)
Git branch for codcel-calculation-engine (e.g. feature/my-branch)
Use --*-engine-branch to point generated code at a development branch. You can mix tags and branches — here the calculation engine uses a feature branch while the other engines use release tags:
The CLI arguments correspond to settings in codcel.toml. The desktop app reads and writes codcel.toml, while the CLI accepts the same values as command-line flags.