NAME
    gcloud alpha beyondcorp client-connector services create - create a new
        BeyondCorp client connector service

SYNOPSIS
    gcloud alpha beyondcorp client-connector services create
        (CLIENT_CONNECTOR_SERVICE : --location=LOCATION)
        (--config-from-file=CONFIG_FROM_FILE
          | [--egress-peered-vpc=EGRESS_PEERED_VPC
          --ingress-config=INGRESS_CONFIG : --display-name=DISPLAY_NAME])
        [--async] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (ALPHA) Create a new BeyondCorp client connector service.

EXAMPLES
    The following command creates a client connector service with ID
    my-service-resource using ingress/egress config provided:

        $ gcloud alpha beyondcorp client-connector services create \
            my-service-resource --location=us-central1 \
            --project=consumer-project-id \
            --ingress-config='{"transportProtocol":"TCP",
         "destinationRoutes":[{"address":"196.0.0.1",
         "netmask":"255.255.255.0"}]}' \
            --egress-peered-vpc='{"networkVpc":"projects/consumer-project-id\
        /global/networks/my-vpc-network"}'

    The following command creates a client connector service with ID
    my-service-resource with configuration from file:

        $ gcloud alpha beyondcorp client-connector services create \
            my-service-resource --project=consumer-project-id \
            --location=us-central1 \
            --config-from-file=/path/to/file/configJson.txt

POSITIONAL ARGUMENTS
     Client connector service resource - The BeyondCorp client connector
     service you want to create. The arguments in this group can be used to
     specify the attributes of this resource. (NOTE) Some attributes are not
     given arguments in this group but can be set in other ways.

     To set the project attribute:
      ◆ provide the argument client_connector_service on the command line
        with a fully specified name;
      ◆ set the property core/project;
      ◆ provide the argument --project on the command line.

     This must be specified.

       CLIENT_CONNECTOR_SERVICE
          ID of the client_connector_service or fully qualified identifier for
          the client_connector_service.

          To set the client_connector_service attribute:
          ▸ provide the argument client_connector_service on the command
            line.

          This positional argument must be specified if any of the other
          arguments in this group are specified.

       --location=LOCATION
          The location of the BeyondCorp Enterprise client connector.

          To set the location attribute:
          ▸ provide the argument client_connector_service on the command line
            with a fully specified name;
          ▸ provide the argument --location on the command line.

REQUIRED FLAGS
     Client connector service configuration.

     Exactly one of these must be specified:

       --config-from-file=CONFIG_FROM_FILE
          Path to json file containing client connector service configuration.
          Example - "/file/path/configJson.txt" where configJson.txt contains -              {
                "ingress":{
                  "config":{
                    "transportProtocol":"TCP",
                    "destinationRoutes":[{
                      "address":"196.0.0.0",
                      "netmask":"255.255.255.0"
                    }]
                  }
                },
                "egress":{
                  "peeredVpc":{
                    "networkVpc":"projects/consumer-project-id/global/networks/my-vpc-network"
                  }
                },
                "displayName":"my-service-resource"
              }

       --egress-peered-vpc=EGRESS_PEERED_VPC
          The peered VPC owned by the consumer project. Example -
          {"networkVpc":
          "projects/consumer-project-id/global/networks/my-vpc-network"}.

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

       --ingress-config=INGRESS_CONFIG
          The basic ingress config for client gateways. Example -
          {"transportProtocol":
          "TCP","destinationRoutes":[{"address":"196.0.0.1",
          "netmask":"255.255.255.0"}]}.

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

       --display-name=DISPLAY_NAME
          An arbitrary user-provided name for the client connector service. The
          display name should follow format -
          ▸ Must be 6 to 30 characters in length.
          ▸ Can only contain lowercase letters, numbers and hyphens.
          ▸ Must start with a letter.

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

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.

API REFERENCE
    This command uses the beyondcorp/v1alpha API. The full documentation for
    this API can be found at: https://cloud.google.com/

NOTES
    This command is currently in alpha and might change without notice. If this
    command fails with API permission errors despite specifying the correct
    project, you might be trying to access an API with an invitation-only early
    access allowlist. This variant is also available:

        $ gcloud beta beyondcorp client-connector services create

