Pipeline
Get a pipeline element's job_config
Changed onReturn one element's job_config, hydrated lazily on expand.
The bulk /elements response projects the bigger keys (parameters, optimizer, cost) out of every element so the details page loads fast; this fills them back in for the one element a drawer is showing. Returns {} for an element that does not exist or is not visible to the caller.
Note this is the DB row, not the storage copy — the two differ only by objectives, the multi-MB serialized measurement payload the worker reads directly and no client needs.
get/pipelines/elements/{element_id}/job_config
Request
- Base URLhttps://api.ionworks.com
- URLhttps://api.ionworks.com/pipelines/elements/{element_id}/job_config
- Authnone declared
Path parameters
element_idstring uuid required
Response
Successful Response
object required
Changes
- breaking
for the
pathrequest parameterelement_id, the format changed from no format touuid
- breaking