Lists the Schedules that match the filter expression. The following
fields are supported:
display_name: Supports =, != comparisons, and : wildcard.
state: Supports = and != comparisons.
request: Supports existence of the <request_type> check.
(e.g. create_pipeline_job_request:* --> Schedule has
create_pipeline_job_request).
create_time: Supports =, !=, <, >, <=, and >= comparisons.
Values must be in RFC 3339 format.
start_time: Supports =, !=, <, >, <=, and >= comparisons.
Values must be in RFC 3339 format.
end_time: Supports =, !=, <, >, <=, >= comparisons and :*
existence check. Values must be in RFC 3339 format.
next_run_time: Supports =, !=, <, >, <=, and >=
comparisons. Values must be in RFC 3339 format.
Filter expressions can be combined together using logical operators
(NOT, AND & OR).
The syntax to define filter expression is based on
https://google.aip.dev/160.
Lists the Schedules that match the filter expression. The following
fields are supported:
display_name: Supports =, != comparisons, and : wildcard.
state: Supports = and != comparisons.
request: Supports existence of the <request_type> check.
(e.g. create_pipeline_job_request:* --> Schedule has
create_pipeline_job_request).
create_time: Supports =, !=, <, >, <=, and >= comparisons.
Values must be in RFC 3339 format.
start_time: Supports =, !=, <, >, <=, and >= comparisons.
Values must be in RFC 3339 format.
end_time: Supports =, !=, <, >, <=, >= comparisons and :*
existence check. Values must be in RFC 3339 format.
next_run_time: Supports =, !=, <, >, <=, and >=
comparisons. Values must be in RFC 3339 format.
Filter expressions can be combined together using logical operators
(NOT, AND & OR).
The syntax to define filter expression is based on
https://google.aip.dev/160.
A comma-separated list of fields to order by. The default sort order is in
ascending order. Use "desc" after a field name for descending. You can have
multiple order_by fields provided.
For example, using "create_time desc, end_time" will order results by
create time in descending order, and if there are multiple schedules having
the same create time, order them by the end time in ascending order.
If order_by is not specified, it will order by default with create_time in
descending order.
A comma-separated list of fields to order by. The default sort order is in
ascending order. Use "desc" after a field name for descending. You can have
multiple order_by fields provided.
For example, using "create_time desc, end_time" will order results by
create time in descending order, and if there are multiple schedules having
the same create time, order them by the end time in ascending order.
If order_by is not specified, it will order by default with create_time in
descending order.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]
