Skip to main content
← Back to list
01Issue
FeatureOpenSwamp CLI
Assigneeskeeb

Docs: repository-configuration.md missing defaultDriver / defaultDriverConfig

Opened by keeb · 4/25/2026

Problem

The .swamp.yaml reference at content/manual/reference/repository-configuration.md documents every field on RepoMarkerData except defaultDriver and defaultDriverConfig. The fields shipped in swamp-club#159 / swamp#1219 and were extended to direct swamp model method run paths in swamp-club#165 / swamp#1221, but the user-facing manual still has no reference.

Proposed solution

Add defaultDriver and defaultDriverConfig to the field table in content/manual/reference/repository-configuration.md. Suggested content:

  • defaultDriver (string, optional) — Repo-level default execution driver. Applied when no higher tier (CLI, step, job, workflow, definition) sets a driver. Example: docker.
  • defaultDriverConfig (object, optional) — Driver-specific configuration paired with defaultDriver. Used as-is — configs are not merged across levels.

Cross-link to the design/execution-drivers.md priority chain (CLI > step > job > workflow > definition > repo > raw). Brief example block:

swampVersion: "..."
initializedAt: "..."
defaultDriver: docker
defaultDriverConfig:
  image: "alpine:latest"

Source of truth

  • Schema: src/infrastructure/persistence/repo_marker_repository.ts:62-67
  • Priority chain: design/execution-drivers.md — Resolution Priority section
  • Behavior coverage: swamp#1221 (extends to direct method runs and adds malformed-YAML failure mode)

Alternatives

None reasonable — the fields are stable user-facing configuration; documentation is the right answer.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

4/25/2026, 7:37:18 PM

No activity in this phase yet.

03Sludge Pulse
keeb assigned keeb4/25/2026, 7:38:41 PM

Sign in to post a ripple.