Data Source: oci_datascience_pipeline_run

This data source provides details about a specific Pipeline Run resource in Oracle Cloud Infrastructure Data Science service.

Gets a PipelineRun by identifier.

Example Usage

data "oci_datascience_pipeline_run" "test_pipeline_run" {
	#Required
	pipeline_run_id = oci_datascience_pipeline_run.test_pipeline_run.id
}

Argument Reference

The following arguments are supported:

• pipeline_run_id - (Required) The OCID of the pipeline run.

Attributes Reference

The following attributes are exported:

• compartment_id - The OCID of the compartment where you want to create the pipeline run.
• 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.
• configuration_override_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 run.
• defined_tags - Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {"Operations.CostCenter": "42"}
• 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 run.
• 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_override_details - The pipeline log configuration details.
  • enable_auto_log_creation - If automatic on-behalf-of log object creation is enabled for pipeline runs.
  • enable_logging - If customer logging is enabled for pipeline.
  • log_group_id - The OCID of the log group.
  • log_id - The OCID of the log.
• log_details - Customer logging details for pipeline run.
  • log_group_id - The log group id for where log objects will be for pipeline runs.
  • log_id - The log id of the log object the pipeline run logs will be shipped to.
• pipeline_id - The OCID of the pipeline for which pipeline run is created.
• project_id - The OCID of the project to associate the pipeline run with.
• state - The current state of the pipeline run.
• step_override_details - Array of step override details. Only Step Configuration is allowed to be overridden.
  • 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_name - The name of the step.
• step_runs - Array of StepRun object for each step.
  • job_run_id - The OCID of the job run triggered for this step run.
  • lifecycle_details - Details of the state of the step run.
  • state - The state of the step run.
  • step_name - The name of the step.
  • step_type - The type of step.
  • time_finished - The date and time the pipeline step run finshed executing in the timestamp format defined by RFC3339.
  • time_started - The date and time the pipeline step run was started in the timestamp format defined by RFC3339.
• system_tags - Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {"orcl-cloud.free-tier-retained": "true"}
• time_accepted - The date and time the pipeline run was accepted in the timestamp format defined by RFC3339.
• time_finished - The date and time the pipeline run request was finished in the timestamp format defined by RFC3339.
• time_started - The date and time the pipeline run request was started in the timestamp format defined by RFC3339.
• time_updated - The date and time the pipeline run was updated in the timestamp format defined by RFC3339.