Dataproc Workflow Template

This table represents the Dataproc Workflow Template resource from Google Cloud Platform.

gcp.dataproc_workflow_template

Fields

TitleIDTypeData TypeDescription
_keycorestring
ancestorscorearray<string>
create_timecoretimestampOutput only. The time template was created.
dag_timeoutcorestringOptional. Timeout duration for the DAG of jobs, expressed in seconds (see JSON representation of duration (https://developers.google.com/protocol-buffers/docs/proto3#json)). The timeout duration must be from 10 minutes ("600s") to 24 hours ("86400s"). The timer begins when the first job is submitted. If the workflow is running at the end of the timeout period, any remaining jobs are cancelled, the workflow is ended, and if the workflow was running on a managed cluster, the cluster is deleted.
datadog_display_namecorestring
encryption_configcorejsonOptional. Encryption settings for encrypting workflow template job arguments.
idcorestring
jobscorejsonRequired. The Directed Acyclic Graph of Jobs to submit.
labelscorearray<string>
namecorestringOutput only. The resource name of the workflow template, as described in https://cloud.google.com/apis/design/resource_names. For projects.regions.workflowTemplates, the resource name of the template has the following format: projects/{project_id}/regions/{region}/workflowTemplates/{template_id} For projects.locations.workflowTemplates, the resource name of the template has the following format: projects/{project_id}/locations/{location}/workflowTemplates/{template_id}
organization_idcorestring
parameterscorejsonOptional. Template parameters whose values are substituted into the template. Values for parameters must be provided when the template is instantiated.
parentcorestring
placementcorejsonRequired. WorkflowTemplate scheduling information.
project_idcorestring
project_numbercorestring
resource_namecorestring
tagscorehstore
update_timecoretimestampOutput only. The time template was last updated.
versioncoreint64Optional. Used to perform a consistent read-modify-write.This field should be left blank for a CreateWorkflowTemplate request. It is required for an UpdateWorkflowTemplate request, and must match the current server version. A typical update template flow would fetch the current template with a GetWorkflowTemplate request, which will return the current template with the version field filled in with the current server version. The user updates other fields in the template, then returns it as part of the UpdateWorkflowTemplate request.