Create Config
Create a new pipeline configuration.
The YAML is validated but validation errors do NOT block persistence — the
config is saved regardless and the validation_report / is_runnable
fields on the response reflect the current state. The run-gate on
POST /configs/{id}/run enforces that invalid configs cannot be executed.
Pure YAML parse errors still return 400 (nothing persistable).
Args: request: Configuration create request service: Execution service (injected) container: Service container (injected)
Returns: Created configuration with validation_report and is_runnable populated.
Raises: HTTPException: 400 on YAML parse error, 500 for server errors
Request Body required
Section titled “Request Body required ”Request to create a new pipeline configuration.
Responses
Section titled “ Responses ”Successful Response
Pipeline configuration response.
Note: Renamed from ConfigResponse to avoid schema collision with SystemConfigResponse.
object
Configuration UUID
Configuration name
Origin of config
SHA-256 hash of config
Version number
Creation timestamp
Last update timestamp
Whether config is active
Validation report returned by the config validator.
Returned verbatim in 200 responses from POST /configs/validate and embedded
in 400 responses from create/update/run endpoints when validation fails.
object
True when no errors present; warnings do not invalidate
All findings, errors first then warnings
A single validation finding emitted by the pipeline config validator.
object
Error or warning
Stable error code (e.g. E202, W501)
Path into the config where the issue was found
Human-readable description of the issue
Deterministic, authoritative remediation guidance
Number of errors
Number of warnings
True when the config passes validation (error_count == 0). Warnings do not invalidate. Mirrors ValidationReport.is_valid.
Validation Error