Validate a resource
Validates an entire pipeline resource file at one of four depths, against the environment named in environmentName. Depth 1 performs basic syntax checking only. Depth 2 additionally resolves basic parameters (using the pipeline’s own variables and their default values) and carries out deeper validation not requiring invocation of the Runner. Depth 3 as Depth 2, but performs full parameter resolution, invoking the Runner to evaluate JavaScript if required. Depth 4 full validation, invoking all Runner capabilities; for transformation pipelines, also populates the SQL cache. Components are validated against the environment’s data warehouse type. Results at depths 1 and 2 are returned synchronously (200 OK). Depths 3 and 4 return immediately (202 Accepted) with a PENDING operationId; poll GET /v1/projects/{projectId}/resource-validations/{operationId} for the aggregated result, or cancel via DELETE. The request body must contain the resource file content with Content-Type: text/plain, and can be at most 10 MB (10,485,760 bytes); a larger file is rejected with 413 Content Too Large. Pipeline YAML files (.orch.yaml, .tran.yaml, .test.yaml) are the only supported resource type today; the plain-text content type is used in anticipation of supporting other resource types (such as SQL scripts or Python source files) in future.
Query Parameters
Body
The body is of type string.
Response
Validation completed (synchronous, depth 1-2)
The result of a resource validation request.