NAME
    gcloud beta services vpc-peerings connect - connect to a service via VPC
        peering for a project network

SYNOPSIS
    gcloud beta services vpc-peerings connect --network=NETWORK --ranges=RANGES
        [--async]
        [--service=SERVICE; default="servicenetworking.googleapis.com"]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) This command connects a private service connection to a service via
    a VPC network.

EXAMPLES
    To connect a network called my-network on the current project to a service
    called your-service with IP CIDR ranges google-range-1,google-range-2 for
    the service to use, run:

        $ gcloud beta services vpc-peerings connect --network=my-network \
            --service=your-service --ranges=google-range-1,google-range-2

    To run the same command asynchronously (non-blocking), run:

        $ gcloud beta services vpc-peerings connect --network=my-network \
            --service=your-service --ranges=google-range-1,google-range-2 \
            --async

REQUIRED FLAGS
     --network=NETWORK
        The network in the current project to be peered with the service

     --ranges=RANGES
        The names of IP CIDR ranges for service to use.

OPTIONAL FLAGS
     --async
        Return immediately, without waiting for the operation in progress to
        complete.

     --service=SERVICE; default="servicenetworking.googleapis.com"
        The service to connect to

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. These
    variants are also available:

        $ gcloud services vpc-peerings connect

        $ gcloud alpha services vpc-peerings connect

