gcloud tasks create-http-task - create and add a task that targets a HTTP endpoint

gcloud tasks create-http-task[TASK_ID]--queue=QUEUE--url=URL[--header=HEADER_FIELD:HEADER_VALUE][--location=LOCATION][--method=METHOD][--schedule-time=SCHEDULE_TIME][--body-content=BODY_CONTENT    |--body-file=BODY_FILE][[--oauth-service-account-email=OAUTH_SERVICE_ACCOUNT_EMAIL :--oauth-token-scope=OAUTH_TOKEN_SCOPE]    | [--oidc-service-account-email=OIDC_SERVICE_ACCOUNT_EMAIL :--oidc-token-audience=OIDC_TOKEN_AUDIENCE]][GCLOUD_WIDE_FLAG …]

[TASK_ID]

The task to create.

If not specified then the system will generate a random unique task ID.Explicitly specifying a task ID enables task de-duplication. If a task's ID isidentical to that of an existing task or a task that was deleted or completedrecently then the call will fail.

Because there is an extra lookup cost to identify duplicate task names, taskscreated with IDs have significantly increased latency. Using hashed strings forthe task ID or for the prefix of the task ID is recommended.

--queue=QUEUE

The queue the task belongs to.

--url=URL

The full URL path that the request will be sent to. This string must begin witheither "http://" or "https://".

--header=HEADER_FIELD:HEADER_VALUE

An HTTP request header. Header values can contain commas. This flag can berepeated. Repeated header fields will have their values overridden.

--location=LOCATION

The location where we want to manage the queue or task. If not specified, usesthe location of the current project's App Engine app if there is an associatedapp.

--method=METHOD

The HTTP method to use for the request. If not specified, "POST" will be used.

--schedule-time=SCHEDULE_TIME

The time when the task is scheduled to be first attempted. Defaults to "now" ifnot specified.

At most one of these can be specified:

--body-content=BODY_CONTENT

HTTP Body data sent to the task worker processing the task.

--body-file=BODY_FILE

File containing HTTP body data sent to the task worker processing the task.

How the request sent to the target when executing the task should beauthenticated.At most one of these can be specified:

OAuth2

--oauth-service-account-email=OAUTH_SERVICE_ACCOUNT_EMAIL

The service account email to be used for generating an OAuth2 access token to beincluded in the request sent to the target when executing the task. The serviceaccount must be within the same project as the queue. The caller must have'iam.serviceAccounts.actAs' permission for the service account.

This flag argument must be specified if any of the other arguments in this groupare specified.

--oauth-token-scope=OAUTH_TOKEN_SCOPE

The scope to be used when generating an OAuth2 access token to be included inthe request sent to the target when executing the task. If not specified,'https://www.googleapis.com/auth/cloud-platform' will be used.

OpenId Connect

--oidc-service-account-email=OIDC_SERVICE_ACCOUNT_EMAIL

The service account email to be used for generating an OpenID Connect token tobe included in the request sent to the target when executing the task. Theservice account must be within the same project as the queue. The caller musthave 'iam.serviceAccounts.actAs' permission for the service account.

This flag argument must be specified if any of the other arguments in this groupare specified.

--oidc-token-audience=OIDC_TOKEN_AUDIENCE

The audience to be used when generating an OpenID Connect token to be includedin the request sent to the target when executing the task. If not specified, theURI specified in the target will be used.

Run$gcloud help for details.