What you would like to accomplish: Add a field or option to configure Cloud Scheduler Job retries directly in The Data Pipelines API.
How this might work: This configuration is only built in for Cloud Scheduler, but other services that use the The Data Pipelines API such as Terraform google_data_pipeline_pipeline manage the Cloud Scheduler jobs automatically, so if The Data Pipelines API does not support the retry configuration, dependent APIs will not have that option either.
If applicable, reasons why alternative solutions are not sufficient: Since the API does not have the option to add retries to the scheduling job, it essentially needs to be done separately.
Other information (workarounds you have tried, documentation consulted, etc):
The Data Pipelines API used to schedule the recurrent Dataflow jobs, does not have a field or option to configure Cloud Scheduler retries:
The doc also mentions to add these retry settings after the corresponding Cloud scheduler job has already been created, as there’s no way to do it on the initial data pipeline scheduling config [2].
Description
Add a field or option to configure Cloud Scheduler Job retries directly in The Data Pipelines API.
How this might work:
This configuration is only built in for Cloud Scheduler, but other services that use the The Data Pipelines API such as Terraform google_data_pipeline_pipeline manage the Cloud Scheduler jobs automatically, so if The Data Pipelines API does not support the retry configuration, dependent APIs will not have that option either.
If applicable, reasons why alternative solutions are not sufficient:
Since the API does not have the option to add retries to the scheduling job, it essentially needs to be done separately.
Other information (workarounds you have tried, documentation consulted, etc):
The Data Pipelines API used to schedule the recurrent Dataflow jobs, does not have a field or option to configure Cloud Scheduler retries:
The doc also mentions to add these retry settings after the corresponding Cloud scheduler job has already been created, as there’s no way to do it on the initial data pipeline scheduling config [2].
References:
[1]
[2]