Package com.google.events.cloud.scheduler.v1 (0.16.0)

App Engine target. The job will be pushed to a job handler by means of an HTTP request via an http_method such as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an HTTP response code in the range [200 - 299]. Error 503 is considered an App Engine system error instead of an application error. Requests returning error 503 will be retried regardless of retry configuration and not counted against retry counts. Any other response code, or a failure to receive a response before the deadline, constitutes a failed attempt.

Protobuf type google.events.cloud.scheduler.v1.AppEngineHttpTarget

App Engine target. The job will be pushed to a job handler by means of an HTTP request via an http_method such as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an HTTP response code in the range [200 - 299]. Error 503 is considered an App Engine system error instead of an application error. Requests returning error 503 will be retried regardless of retry configuration and not counted against retry counts. Any other response code, or a failure to receive a response before the deadline, constitutes a failed attempt.

Protobuf type google.events.cloud.scheduler.v1.AppEngineHttpTarget

App Engine Routing. For more information about services, versions, and instances see An Overview of App Engine, Microservices Architecture on Google App Engine, App Engine Standard request routing, and App Engine Flex request routing.

Protobuf type google.events.cloud.scheduler.v1.AppEngineRouting

App Engine Routing. For more information about services, versions, and instances see An Overview of App Engine, Microservices Architecture on Google App Engine, App Engine Standard request routing, and App Engine Flex request routing.

Protobuf type google.events.cloud.scheduler.v1.AppEngineRouting

Http target. The job will be pushed to the job handler by means of an HTTP request via an http_method such as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an HTTP response code in the range [200 - 299]. A failure to receive a response constitutes a failed execution. For a redirected request, the response returned by the redirected request is considered.

Protobuf type google.events.cloud.scheduler.v1.HttpTarget

Http target. The job will be pushed to the job handler by means of an HTTP request via an http_method such as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an HTTP response code in the range [200 - 299]. A failure to receive a response constitutes a failed execution. For a redirected request, the response returned by the redirected request is considered.

Protobuf type google.events.cloud.scheduler.v1.HttpTarget

Configuration for a job. The maximum allowed size for a job is 1MB.

Protobuf type google.events.cloud.scheduler.v1.Job

Configuration for a job. The maximum allowed size for a job is 1MB.

Protobuf type google.events.cloud.scheduler.v1.Job

The data within all Job events.

Protobuf type google.events.cloud.scheduler.v1.JobEventData

The data within all Job events.

Protobuf type google.events.cloud.scheduler.v1.JobEventData

Contains information needed for generating an OAuth token. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.

Protobuf type google.events.cloud.scheduler.v1.OAuthToken

Contains information needed for generating an OAuth token. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.

Protobuf type google.events.cloud.scheduler.v1.OAuthToken

Contains information needed for generating an OpenID Connect token. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself.

Protobuf type google.events.cloud.scheduler.v1.OidcToken

Contains information needed for generating an OpenID Connect token. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself.

Protobuf type google.events.cloud.scheduler.v1.OidcToken

Pub/Sub target. The job will be delivered by publishing a message to the given Pub/Sub topic.

Protobuf type google.events.cloud.scheduler.v1.PubsubTarget

Pub/Sub target. The job will be delivered by publishing a message to the given Pub/Sub topic.

Protobuf type google.events.cloud.scheduler.v1.PubsubTarget

Settings that determine the retry behavior. By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.

Protobuf type google.events.cloud.scheduler.v1.RetryConfig

Settings that determine the retry behavior. By default, if a job does not complete successfully (meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings in RetryConfig.

Protobuf type google.events.cloud.scheduler.v1.RetryConfig

Scheduler job data.

Protobuf type google.events.cloud.scheduler.v1.SchedulerJobData

Scheduler job data.

Protobuf type google.events.cloud.scheduler.v1.SchedulerJobData

The HTTP method used to execute the job.

Protobuf enum google.events.cloud.scheduler.v1.HttpMethod

State of the job.

Protobuf enum google.events.cloud.scheduler.v1.Job.State