List Configs
List all active pipeline configurations with pagination.
Each entry carries a validation_report and is_runnable field re-derived
against the current adapter registry. Registry drift (a renamed/removed
adapter) is surfaced automatically without requiring a user re-save.
Args: service: Execution service (injected) container: Service container (injected) limit: Maximum number of results per page (default: 100) offset: Number of records to skip for pagination (default: 0)
Returns: Paginated list of configurations with total count
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Maximum results per page
Maximum results per page
Number of records to skip
Number of records to skip
Responses
Section titled “ Responses ”Successful Response
Paginated list of pipeline configurations.
object
Total number of configurations matching filters
Maximum entries per page
Offset from start
Whether more configurations exist
List of configurations
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