Get Config
Get detailed pipeline configuration.
The response includes a validation_report re-derived from the current
adapter registry, so registry drift is visible even for configs that were
valid when saved.
Args: config_id: Configuration UUID service: Execution service (injected) container: Service container (injected)
Returns: Configuration details including YAML content and current validation state
Raises: HTTPException: 404 if not found
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”Successful Response
Detailed configuration response including YAML content.
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.
Full YAML content
Resource not found
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.
Validation Error