gcloud scheduler jobs create pubsub <JOB>

Create a Cloud Scheduler job with a Pub/Sub target


JOBID of the job or fully qualified identifier for the job


--account <ACCOUNT>Google Cloud Platform user account to use for invocation. Overrides the default *core/account* property value for this command invocation
--attributes <ATTRIBUTES>Comma-separated list of attributes. Each attribute has the form "NAME=VALUE". You can specify up to 100 attributes
--billing-project <BILLING_PROJECT>The Google Cloud Platform project that will be charged quota for operations performed in gcloud. If you need to operate on one project, but need quota against a different project, you can use this flag to specify the billing project. If both `billing/quota_project` and `--billing-project` are specified, `--billing-project` takes precedence. Run `$ gcloud config set --help` to see more information about `billing/quota_project`
--configuration <CONFIGURATION>The configuration to use for this command invocation. For more information on how to use configurations, run: `gcloud topic configurations`. You can also use the CLOUDSDK_ACTIVE_CONFIG_NAME environment variable to set the equivalent of this flag for a terminal session
--description <DESCRIPTION>Human-readable description of the job
--flags-file <YAML_FILE>A YAML or JSON file that specifies a *--flag*:*value* dictionary. Useful for specifying complex flag values with special characters that work with any command interpreter. Additionally, each *--flags-file* arg is replaced by its constituent flags. See $ gcloud topic flags-file for more information
--flatten <KEY>Flatten _name_[] output resource slices in _KEY_ into separate records for each item in each slice. Multiple keys and slices may be specified. This also flattens keys for *--format* and *--filter*. For example, *--flatten=abc.def* flattens *abc.def[].ghi* references to *abc.def.ghi*. A resource record containing *abc.def[]* with N elements will expand to N records in the flattened output. This flag interacts with other flags that are applied in this order: *--flatten*, *--sort-by*, *--filter*, *--limit*
--format <FORMAT>Set the format for printing command output resources. The default is a command-specific human-friendly output format. The supported formats are: `config`, `csv`, `default`, `diff`, `disable`, `flattened`, `get`, `json`, `list`, `multi`, `none`, `object`, `table`, `text`, `value`, `yaml`. For more details run $ gcloud topic formats
--helpDisplay detailed help
--impersonate-service-account <SERVICE_ACCOUNT_EMAIL>For this gcloud invocation, all API requests will be made as the given service account instead of the currently selected account. This is done without needing to create, download, and activate a key for the account. In order to perform operations as the service account, your currently selected account must have an IAM role that includes the iam.serviceAccounts.getAccessToken permission for the service account. The roles/iam.serviceAccountTokenCreator role has this permission or you may create a custom role. Overrides the default *auth/impersonate_service_account* property value for this command invocation
--log-httpLog all HTTP server requests and responses to stderr. Overrides the default *core/log_http* property value for this command invocation
--max-backoff <MAX_BACKOFF>Maximum amount of time to wait before retrying a task after it fails. For example, `10m`. Default is `1h`
--max-doublings <MAX_DOUBLINGS>Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant
--max-retry-attempts <MAX_RETRY_ATTEMPTS>Number of times to retry the request if it fails or times out. Must be in range 0-5 inclusive. Default is 0
--max-retry-duration <MAX_RETRY_DURATION>Time limit for retrying a failed task, measured from when the task was first run. If specified with `--max-retry-attempts` greater than 0, the task will be retried until both limits are reached. Default is 0 (which means unlimited)
--message-body <MESSAGE_BODY>Body of the message
--message-body-from-file <MESSAGE_BODY_FROM_FILE>Path to a file containing the body of the message
--min-backoff <MIN_BACKOFF>Minimum amount of time to wait before retrying a task after it fails. For example, `10s`. Default is `5s`
--project <PROJECT_ID>The Google Cloud Platform project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be listed using `gcloud config list --format='text(core.project)'` and can be set using `gcloud config set project PROJECTID`. + `--project` and its fallback `core/project` property play two roles in the invocation. It specifies the project of the resource to operate on. It also specifies the project for API enablement check, quota, and billing. To specify a different project for quota and billing, use `--billing-project` or `billing/quota_project` property
--quietDisable all interactive prompts when running gcloud commands. If input is required, defaults will be used, or an error will be raised. Overrides the default core/disable_prompts property value for this command invocation. This is equivalent to setting the environment variable `CLOUDSDK_CORE_DISABLE_PROMPTS` to 1
--schedule <SCHEDULE>Schedule on which the job will be executed. + As a general rule, execution `n + 1` of a job will not begin until execution `n` has finished. Cloud Scheduler will never allow two simultaneously outstanding executions. For example, this implies that if the `n+1` execution is scheduled to run at `16:00` but the `n` execution takes until `16:15`, the `n+1` execution will not start until `16:15`. A scheduled start time will be delayed if the previous execution has not ended when its scheduled time occurs. + If --retry-count > 0 and a job attempt fails, the job will be tried a total of --retry-count times, with exponential backoff, until the next scheduled start time. + The schedule can be either of the following types: * Crontab: http://en.wikipedia.org/wiki/Cron#Overview * English-like schedule: https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule
--time-zone <TIME_ZONE>Specifies the time zone to be used in interpreting --schedule. The value of this field must be a time zone name from the tz database (http://en.wikipedia.org/wiki/Tz_database). + Note that some time zones include a provision for daylight savings time. The rules for daylight saving time are determined by the chosen time zone. + For UTC use the string "utc". Default is "utc"
--topic <TOPIC>Name of the Google Cloud Pub/Sub topic to publish to when the job runs
--trace-token <TRACE_TOKEN>Token used to route traces of service requests for investigation of issues. Overrides the default *core/trace_token* property value for this command invocation
--user-output-enabledPrint user intended output to the console. Overrides the default *core/user_output_enabled* property value for this command invocation. Use *--no-user-output-enabled* to disable
--verbosity <VERBOSITY>Override the default verbosity for this command. Overrides the default *core/verbosity* property value for this command invocation. _VERBOSITY_ must be one of: *debug*, *info*, *warning*, *error*, *critical*, *none*