The OCID of the compartment where you want to create the pipeline.
The OCID of the user who created the pipeline.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A short description of the pipeline.
A user-friendly display name for the resource.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. See Resource Tags. Example: {@code {"Department": "Finance"}}
The OCID of the pipeline.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in 'Failed' state.
The current state of the pipeline.
The OCID of the project to associate the pipeline with.
Array of step details for each step.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time the resource was created in the timestamp format defined by RFC3339. Example: 2020-08-06T21:10:29.41Z
The date and time the resource was updated in the timestamp format defined by RFC3339. Example: 2020-08-06T21:10:29.41Z
A Pipeline to orchestrate and execute machine learning workflows.