NAME
    gcloud beta dataflow yaml run - runs a job from the specified path

SYNOPSIS
    gcloud beta dataflow yaml run JOB_NAME
        (--yaml-pipeline=YAML_PIPELINE
          | --yaml-pipeline-file=YAML_PIPELINE_FILE)
        [--jinja-variables=JSON_OBJECT]
        [--pipeline-options=[OPTIONS=VALUE;OPTION=VALUE,...]]
        [--region=REGION_ID] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) Runs a job from the specified YAML description or Cloud Storage
    path.

EXAMPLES
    To run a job from YAML, run:

        $ gcloud beta dataflow yaml run my-job \
            --yaml-pipeline-file=gs://yaml-path --region=europe-west1

POSITIONAL ARGUMENTS
     JOB_NAME
        Unique name to assign to the job.

REQUIRED FLAGS
     Exactly one of these must be specified:

       --yaml-pipeline=YAML_PIPELINE
          Inline definition of the YAML pipeline to run.

       --yaml-pipeline-file=YAML_PIPELINE_FILE
          Path of a file defining the YAML pipeline to run. (Must be a local
          file or a URL beginning with 'gs://'.)

OPTIONAL FLAGS
     --jinja-variables=JSON_OBJECT
        Jinja2 variables to be used in reifying the yaml.

     --pipeline-options=[OPTIONS=VALUE;OPTION=VALUE,...]
        Pipeline options to pass to the job.

     --region=REGION_ID
        Region ID of the job's regional endpoint. Defaults to 'us-central1'.

GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
    --help, --impersonate-service-account, --log-http, --project, --quiet,
    --trace-token, --user-output-enabled, --verbosity.

    Run $ gcloud help for details.

NOTES
    This command is currently in beta and might change without notice. This
    variant is also available:

        $ gcloud dataflow yaml run

