Http target. The job will be pushed to the job handler by means of an HTTP request via an [http_method][google.cloud.scheduler.v1beta1.HttpTarget.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.
Which HTTP method to use for the request.
HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod.
If specified, an OAuth token
<https://developers.google.com/identity/protocols/OAuth2>__
will be generated and attached as an Authorization header
in the HTTP request. This type of authorization should be
used when sending requests to a GCP endpoint.
Classes
HeadersEntry
API documentation for scheduler_v1beta1.types.HttpTarget.HeadersEntry class.