cli_profile — a placeholder filled by the configuration itself

Sources: examples/workflow_cli_profile — settings in workflows/cli_profile/.

workflows:
  - cli_profile/default
  - cli_profile/aggressive

The workflow does not touch its sources at all. Instead, the command carries a placeholder named after the workflow:

# This workflow intentionally does not replace source files; it demonstrates
# command placeholder substitution from the workflow config file itself.
use_parameters: No

tasks:
  - name: main
    commands:
      - python3 run_profile.py --profile "${workflow_cli_profile}" --tag "config-placeholder-demo"

${workflow_cli_profile} is filled with the content of the selected configuration file — default.txt holds balanced profile, aggressive.txt holds aggressive profile — so cli_profile/default and cli_profile/aggressive run the same script with different arguments.

This is the simplest form of parameterization there is: one value, chosen by configuration, passed on the command line, with nothing written into any file.

The metrics mix a string and two numbers, one of them derived from the profile name by the script itself:

metrics:
  profile:
    type: regex
    settings:
      file: output.txt
      pattern: "profile: (.*)"
      group_id: 1

  complexity_score:
    type: regex
    settings:
      file: output.txt
      pattern: "complexity_score: ([0-9.]+)"
      group_id: 1
    format: "%.3f"

Where to go next