Data Source: oci_datascience_pipelines
This data source provides the list of Pipelines in Oracle Cloud Infrastructure Data Science service.
Returns a list of Pipelines.
Example Usage
data "oci_datascience_pipelines" "test_pipelines" {
#Required
compartment_id = var.compartment_id
#Optional
created_by = var.pipeline_created_by
display_name = var.pipeline_display_name
id = var.pipeline_id
project_id = oci_datascience_project.test_project.id
state = var.pipeline_state
}
Argument Reference
The following arguments are supported:
compartment_id- (Required) Filter results by the OCID of the compartment.created_by- (Optional) Filter results by the OCID of the user who created the resource.display_name- (Optional) Filter results by its user-friendly name.id- (Optional) Filter results by OCID. Must be an OCID of the correct type for the resource type.project_id- (Optional) Filter results by the OCID of the project.state- (Optional) The current state of the Pipeline.
Attributes Reference
The following attributes are exported:
pipelines- The list of pipelines.
Pipeline Reference
The following attributes are exported:
compartment_id- The OCID of the compartment where you want to create the pipeline.configuration_details- The configuration details of a pipeline.command_line_arguments- The command line arguments to set for steps in the pipeline.environment_variables- Environment variables to set for steps in the pipeline.maximum_runtime_in_minutes- A time bound for the execution of the entire Pipeline. Timer starts when the Pipeline Run is in progress.type- The type of pipeline.
created_by- The OCID of the user who created the pipeline.defined_tags- Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example:{"Operations.CostCenter": "42"}description- A short description of the pipeline.display_name- A user-friendly display name for the resource.freeform_tags- 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:{"Department": "Finance"}id- The OCID of the pipeline.infrastructure_configuration_details- The infrastructure configuration details of a pipeline or a step.block_storage_size_in_gbs- The size of the block storage volume to attach to the instance.block_storage_size_in_gbs_parameterized- The size of the block storage volume to attach to the pipeline step run instance specified as a parameter. This overrides the blockStorageSizeInGBs value. The request will fail if the parameters used are null or invalid.shape_config_details- Details for the pipeline step run shape configuration. Specify only when a flex shape is selected.cpu_baseline- The baseline OCPU utilization for a subcore burstable VM instance. If this attribute is left blank, it will default toBASELINE_1_1. The following values are supported: BASELINE_1_8 - baseline usage is 1⁄8 of an OCPU. BASELINE_1_2 - baseline usage is 1⁄2 of an OCPU. BASELINE_1_1 - baseline usage is an entire OCPU. This represents a non-burstable instance.memory_in_gbs- The total amount of memory available to the pipeline step run instance GBs.memory_in_gbs_parameterized- The total amount of memory available to the pipeline step run instance in GBs specified as a parameter. This overrides the memoryInGBs value. The request will fail if the parameters used are null or invalid.ocpus- The total number of OCPUs available to the pipeline step run instance.ocpus_parameterized- The total number of OCPUs available to the pipeline step run instance specified as a parameter. This overrides the ocpus value. The request will fail if the parameters used are null or invalid.
shape_name- The shape used to launch the instance for all step runs in the pipeline.subnet_id- The subnet to create a secondary vnic in to attach to the instance running the pipeline step.
lifecycle_details- A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in ‘Failed’ state.log_configuration_details- The pipeline log configuration details.parameters- Parameters used in the pipeline.project_id- The OCID of the project to associate the pipeline with.state- The current state of the pipeline.step_details- Array of step details for each step.application_id- The OCID of the dataflow application to be used as a step.depends_on- The list of step names this current step depends on for execution.description- A short description of the step.is_artifact_uploaded- A flag to indicate whether the artifact has been uploaded for this step or not.job_id- The OCID of the job to be used as a step.step_configuration_details- The configuration details of a step.command_line_arguments- The command line arguments to set for step.environment_variables- Environment variables to set for step.maximum_runtime_in_minutes- A time bound for the execution of the step.
step_container_configuration_details- Container Details for a step in pipeline.cmd- The container image run CMD as a list of strings. UseCMDas arguments to theENTRYPOINTor the only command to run in the absence of anENTRYPOINT. The combined size ofCMDandENTRYPOINTmust be less than 2048 bytes.container_type- The type of container.entrypoint- The container image run ENTRYPOINT as a list of strings. Accept theCMDas extra arguments. The combined size ofCMDandENTRYPOINTmust be less than 2048 bytes. More information on howCMDandENTRYPOINTinteract are here.image- The full path to the Oracle Container Repository (OCIR) registry, image, and tag in a canonical format.image_digest- The digest of the container image. For example,sha256:881303a6b2738834d795a32b4a98eb0e5e3d1cad590a712d1e04f9b2fa90a030image_signature_id- OCID of the container image signature
step_dataflow_configuration_details- The configuration details of a Dataflow step.configuration- The Spark configuration passed to the running process.driver_shape- The VM shape for the driver.driver_shape_config_details- Details for the pipeline step run shape configuration. Specify only when a flex shape is selected.cpu_baseline- The baseline OCPU utilization for a subcore burstable VM instance. If this attribute is left blank, it will default toBASELINE_1_1. The following values are supported: BASELINE_1_8 - baseline usage is 1⁄8 of an OCPU. BASELINE_1_2 - baseline usage is 1⁄2 of an OCPU. BASELINE_1_1 - baseline usage is an entire OCPU. This represents a non-burstable instance.memory_in_gbs- The total amount of memory available to the pipeline step run instance GBs.memory_in_gbs_parameterized- The total amount of memory available to the pipeline step run instance in GBs specified as a parameter. This overrides the memoryInGBs value. The request will fail if the parameters used are null or invalid.ocpus- The total number of OCPUs available to the pipeline step run instance.ocpus_parameterized- The total number of OCPUs available to the pipeline step run instance specified as a parameter. This overrides the ocpus value. The request will fail if the parameters used are null or invalid.
executor_shape- The VM shape for the executors.executor_shape_config_details- Details for the pipeline step run shape configuration. Specify only when a flex shape is selected.cpu_baseline- The baseline OCPU utilization for a subcore burstable VM instance. If this attribute is left blank, it will default toBASELINE_1_1. The following values are supported: BASELINE_1_8 - baseline usage is 1⁄8 of an OCPU. BASELINE_1_2 - baseline usage is 1⁄2 of an OCPU. BASELINE_1_1 - baseline usage is an entire OCPU. This represents a non-burstable instance.memory_in_gbs- The total amount of memory available to the pipeline step run instance GBs.memory_in_gbs_parameterized- The total amount of memory available to the pipeline step run instance in GBs specified as a parameter. This overrides the memoryInGBs value. The request will fail if the parameters used are null or invalid.ocpus- The total number of OCPUs available to the pipeline step run instance.ocpus_parameterized- The total number of OCPUs available to the pipeline step run instance specified as a parameter. This overrides the ocpus value. The request will fail if the parameters used are null or invalid.
logs_bucket_uri- An Oracle Cloud Infrastructure URI of the bucket where the Spark job logs are to be uploaded.num_executors- The number of executor VMs requested.warehouse_bucket_uri- An Oracle Cloud Infrastructure URI of the bucket to be used as default warehouse directory for BATCH SQL runs.
step_infrastructure_configuration_details- The infrastructure configuration details of a pipeline or a step.block_storage_size_in_gbs- The size of the block storage volume to attach to the instance.block_storage_size_in_gbs_parameterized- The size of the block storage volume to attach to the pipeline step run instance specified as a parameter. This overrides the blockStorageSizeInGBs value. The request will fail if the parameters used are null or invalid.shape_config_details- Details for the pipeline step run shape configuration. Specify only when a flex shape is selected.cpu_baseline- The baseline OCPU utilization for a subcore burstable VM instance. If this attribute is left blank, it will default toBASELINE_1_1. The following values are supported: BASELINE_1_8 - baseline usage is 1⁄8 of an OCPU. BASELINE_1_2 - baseline usage is 1⁄2 of an OCPU. BASELINE_1_1 - baseline usage is an entire OCPU. This represents a non-burstable instance.memory_in_gbs- The total amount of memory available to the pipeline step run instance GBs.memory_in_gbs_parameterized- The total amount of memory available to the pipeline step run instance in GBs specified as a parameter. This overrides the memoryInGBs value. The request will fail if the parameters used are null or invalid.ocpus- The total number of OCPUs available to the pipeline step run instance.ocpus_parameterized- The total number of OCPUs available to the pipeline step run instance specified as a parameter. This overrides the ocpus value. The request will fail if the parameters used are null or invalid.
shape_name- The shape used to launch the instance for all step runs in the pipeline.subnet_id- The subnet to create a secondary vnic in to attach to the instance running the pipeline step.
step_name- The name of the step. It must be unique within the pipeline. This is used to create the pipeline DAG.step_parameters- Pipeline step parameter detailsoutput- Pipeline output parameter detailsoutput_file- Output file nameoutput_parameter_type- Type of output parametersparameter_names- The list of parameter names that will be output by this step
parameter_type- Type of step parameter
step_run_name- Name used when creating the steprun.step_storage_mount_configuration_details_list- The storage mount details to mount to the instance running the pipeline step.bucket- The object storage bucketdestination_directory_name- The local directory name to be mounteddestination_path- The local path of the mounted directory, excluding directory name.export_id- OCID of the exportmount_target_id- OCID of the mount targetnamespace- The object storage namespaceprefix- Prefix in the bucket to mountstorage_type- The type of storage.
step_type- The type of step.
storage_mount_configuration_details_list- The storage mount details to mount to the instance running the pipeline step.bucket- The object storage bucketdestination_directory_name- The local directory name to be mounteddestination_path- The local path of the mounted directory, excluding directory name.export_id- OCID of the exportmount_target_id- OCID of the mount targetnamespace- The object storage namespaceprefix- Prefix in the bucket to mountstorage_type- The type of storage.
system_tags- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:{"orcl-cloud.free-tier-retained": "true"}time_created- The date and time the resource was created in the timestamp format defined by RFC3339. Example: 2020-08-06T21:10:29.41Ztime_updated- The date and time the resource was updated in the timestamp format defined by RFC3339. Example: 2020-08-06T21:10:29.41Z