gcloud: Wed Jul 30 10:59:26 UTC 2025

gcloud/beta/beyondcorp/security-gateways/applications/create

@@ -0,0 +1,149 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications create - create
+        applications
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications create
+        (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY)
+        --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] [--async]
+        [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID]
+        [--upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create an application
+
+EXAMPLES
+    To create the application, run:
+
+        $ gcloud beta beyondcorp security-gateways applications create
+
+POSITIONAL ARGUMENTS
+     Application resource - Identifier. Name of the resource. 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 application on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       APPLICATION
+          ID of the application or fully qualified identifier for the
+          application.
+
+          To set the application attribute:
+          ▸ provide the argument application 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 id of the application resource. We support only global
+          location.
+
+          To set the location attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line.
+
+       --security-gateway=SECURITY_GATEWAY
+          The securityGateway id of the application resource.
+
+          To set the security-gateway attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --security-gateway on the command line.
+
+REQUIRED FLAGS
+     --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+        Required, Endpoint matchers associated with an application. A
+        combination of hostname and ports as endpoint matchers is used to match
+        the application. Match conditions for OR logic. An array of match
+        conditions to allow for multiple matching criteria. The rule is
+        considered a match if one of the conditions is met. The conditions can
+        be one of the following combinations (Hostname), (Hostname & Ports)
+
+        EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname and
+        Ports - ("example.com" and "22"), ("example.com" and "22,33") etc.
+
+         hostname
+            Hostname of the application.
+
+         ports
+            Ports of the application.
+
+        Shorthand Example:
+
+            --endpoint-matchers=hostname=string,ports=[int] --endpoint-matchers=hostname=string,ports=[int]
+
+        JSON Example:
+
+            --endpoint-matchers='[{"hostname": "string", "ports": [int]}]'
+
+        File Example:
+
+            --endpoint-matchers=path_to_file.(yaml|json)
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        An arbitrary user-provided name for the Application resource. Cannot
+        exceed 64 characters.
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore request if it has already been completed. The server will
+        guarantee that for at least 60 minutes since the first request.
+
+     --upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+        Which upstream resources to forward traffic to.
+
+         egressPolicy
+            Routing policy information.
+
+             regions
+                List of the regions where the application sends traffic.
+
+         network
+            Network to forward traffic to.
+
+             name
+                Network name is of the format:
+                projects/{project}/global/networks/{network}.
+
+        Shorthand Example:
+
+            --upstreams=egressPolicy={regions=[string]},network={name=string} --upstreams=egressPolicy={regions=[string]},network={name=string}
+
+        JSON Example:
+
+            --upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]'
+
+        File Example:
+
+            --upstreams=path_to_file.(yaml|json)
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/applications/delete

@@ -0,0 +1,98 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications delete - delete
+        applications
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications delete
+        (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY)
+        [--async] [--request-id=REQUEST_ID] [--validate-only]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Delete an application
+
+EXAMPLES
+    To delete the application, run:
+
+        $ gcloud beta beyondcorp security-gateways applications delete
+
+POSITIONAL ARGUMENTS
+     Application resource - Name of the resource. 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 application on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       APPLICATION
+          ID of the application or fully qualified identifier for the
+          application.
+
+          To set the application attribute:
+          ▸ provide the argument application 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 id of the application resource. We support only global
+          location.
+
+          To set the location attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line.
+
+       --security-gateway=SECURITY_GATEWAY
+          The securityGateway id of the application resource.
+
+          To set the security-gateway attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --security-gateway on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore the request if it has already been completed. The server will
+        guarantee that for at least 60 minutes after the first request.
+
+        For example, consider a situation where you make an initial request and
+        the request times out. If you make the request again with the same
+        request ID, the server can check if original operation with the same
+        request ID was received, and if so, will ignore the second request.
+        This prevents clients from accidentally creating duplicate commitments.
+
+        The request ID must be a valid UUID with the exception that zero UUID
+        is not supported (00000000-0000-0000-0000-000000000000).
+
+     --validate-only
+        If set, validates request by executing a dry-run which would not alter
+        the resource in any way.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/applications/describe

@@ -0,0 +1,75 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications describe - describe
+        applications
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications describe
+        (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY)
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Describe an application
+
+EXAMPLES
+    To describe the application, run:
+
+        $ gcloud beta beyondcorp security-gateways applications describe
+
+POSITIONAL ARGUMENTS
+     Application resource - The resource name of the Application using the
+     form:
+     projects/{project_id}/locations/global/securityGateway/{security_gateway_id}/applications/{application_id}
+     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 application on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       APPLICATION
+          ID of the application or fully qualified identifier for the
+          application.
+
+          To set the application attribute:
+          ▸ provide the argument application 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 id of the application resource. We support only global
+          location.
+
+          To set the location attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line.
+
+       --security-gateway=SECURITY_GATEWAY
+          The securityGateway id of the application resource.
+
+          To set the security-gateway attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --security-gateway on the command line.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/applications/help

@@ -0,0 +1,37 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications - manage Application
+        resources
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Manage Application resources.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create applications.
+
+     delete
+        (BETA) Delete applications.
+
+     describe
+        (BETA) Describe applications.
+
+     list
+        (BETA) List applications.
+
+     update
+        (BETA) Update applications.
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/applications/list

@@ -0,0 +1,100 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications list - list
+        applications
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications list
+        (--security-gateway=SECURITY_GATEWAY : --location=LOCATION)
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) List applications
+
+EXAMPLES
+    To list all applications, run:
+
+        $ gcloud beta beyondcorp security-gateways applications list
+
+REQUIRED FLAGS
+     SecurityGateway resource - The parent location to which the resources
+     belong.
+     projects/{project_id}/locations/global/securityGateways/{security_gateway_id}
+     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 --security-gateway on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       --security-gateway=SECURITY_GATEWAY
+          ID of the securityGateway or fully qualified identifier for the
+          securityGateway.
+
+          To set the security-gateway attribute:
+          ▸ provide the argument --security-gateway on the command line.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --location=LOCATION
+          The location id of the securityGateway resource. We support only
+          global location.
+
+          To set the location attribute:
+          ▸ provide the argument --security-gateway on the command line with
+            a fully specified name;
+          ▸ provide the argument --location on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/applications/update

@@ -0,0 +1,304 @@
+NAME
+    gcloud beta beyondcorp security-gateways applications update - update
+        applications
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways applications update
+        (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY)
+        [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID]
+        [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+          | --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+          --clear-endpoint-matchers
+          | --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]]
+        [--upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+          | --add-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+          --clear-upstreams
+          | --remove-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Update an application
+
+EXAMPLES
+    To update the application, run:
+
+        $ gcloud beta beyondcorp security-gateways applications update
+
+POSITIONAL ARGUMENTS
+     Application resource - Identifier. Name of the resource. 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 application on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       APPLICATION
+          ID of the application or fully qualified identifier for the
+          application.
+
+          To set the application attribute:
+          ▸ provide the argument application 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 id of the application resource. We support only global
+          location.
+
+          To set the location attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --location on the command line.
+
+       --security-gateway=SECURITY_GATEWAY
+          The securityGateway id of the application resource.
+
+          To set the security-gateway attribute:
+          ▸ provide the argument application on the command line with a fully
+            specified name;
+          ▸ provide the argument --security-gateway on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        An arbitrary user-provided name for the Application resource. Cannot
+        exceed 64 characters.
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore the request if it has already been completed. The server will
+        guarantee that for at least 60 minutes after the first request.
+
+        For example, consider a situation where you make an initial request and
+        the request timed out. If you make the request again with the same
+        request ID, the server can check if original operation with the same
+        request ID was received, and if so, will ignore the second request.
+        This prevents clients from accidentally creating duplicate commitments.
+
+        The request ID must be a valid UUID with the exception that zero UUID
+        is not supported (00000000-0000-0000-0000-000000000000).
+
+     Update endpoint_matchers.
+
+     At most one of these can be specified:
+
+       --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+          Set endpoint_matchers to new value. Endpoint matchers associated with
+          an application. A combination of hostname and ports as endpoint
+          matchers is used to match the application. Match conditions for OR
+          logic. An array of match conditions to allow for multiple matching
+          criteria. The rule is considered a match if one of the conditions is
+          met. The conditions can be one of the following combinations
+          (Hostname), (Hostname & Ports)
+
+          EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname
+          and Ports - ("example.com" and "22"), ("example.com" and "22,33")
+          etc.
+
+           hostname
+              Hostname of the application.
+
+           ports
+              Ports of the application.
+
+          Shorthand Example:
+
+              --endpoint-matchers=hostname=string,ports=[int] --endpoint-matchers=hostname=string,ports=[int]
+
+          JSON Example:
+
+              --endpoint-matchers='[{"hostname": "string", "ports": [int]}]'
+
+          File Example:
+
+              --endpoint-matchers=path_to_file.(yaml|json)
+
+       --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+          Add new value to endpoint_matchers list. Endpoint matchers associated
+          with an application. A combination of hostname and ports as endpoint
+          matchers is used to match the application. Match conditions for OR
+          logic. An array of match conditions to allow for multiple matching
+          criteria. The rule is considered a match if one of the conditions is
+          met. The conditions can be one of the following combinations
+          (Hostname), (Hostname & Ports)
+
+          EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname
+          and Ports - ("example.com" and "22"), ("example.com" and "22,33")
+          etc.
+
+           hostname
+              Hostname of the application.
+
+           ports
+              Ports of the application.
+
+          Shorthand Example:
+
+              --add-endpoint-matchers=hostname=string,ports=[int] --add-endpoint-matchers=hostname=string,ports=[int]
+
+          JSON Example:
+
+              --add-endpoint-matchers='[{"hostname": "string", "ports": [int]}]'
+
+          File Example:
+
+              --add-endpoint-matchers=path_to_file.(yaml|json)
+
+       At most one of these can be specified:
+
+         --clear-endpoint-matchers
+            Clear endpoint_matchers value and set to empty list.
+
+         --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+            Remove existing value from endpoint_matchers list. Endpoint
+            matchers associated with an application. A combination of hostname
+            and ports as endpoint matchers is used to match the application.
+            Match conditions for OR logic. An array of match conditions to
+            allow for multiple matching criteria. The rule is considered a
+            match if one of the conditions is met. The conditions can be one of
+            the following combinations (Hostname), (Hostname & Ports)
+
+            EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname
+            and Ports - ("example.com" and "22"), ("example.com" and "22,33")
+            etc.
+
+             hostname
+                Hostname of the application.
+
+             ports
+                Ports of the application.
+
+            Shorthand Example:
+
+                --remove-endpoint-matchers=hostname=string,ports=[int] --remove-endpoint-matchers=hostname=string,ports=[int]
+
+            JSON Example:
+
+                --remove-endpoint-matchers='[{"hostname": "string", "ports": [int]}]'
+
+            File Example:
+
+                --remove-endpoint-matchers=path_to_file.(yaml|json)
+
+     Update upstreams.
+
+     At most one of these can be specified:
+
+       --upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+          Set upstreams to new value. Which upstream resources to forward
+          traffic to.
+
+           egressPolicy
+              Routing policy information.
+
+               regions
+                  List of the regions where the application sends traffic.
+
+           network
+              Network to forward traffic to.
+
+               name
+                  Network name is of the format:
+                  projects/{project}/global/networks/{network}.
+
+          Shorthand Example:
+
+              --upstreams=egressPolicy={regions=[string]},network={name=string} --upstreams=egressPolicy={regions=[string]},network={name=string}
+
+          JSON Example:
+
+              --upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]'
+
+          File Example:
+
+              --upstreams=path_to_file.(yaml|json)
+
+       --add-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+          Add new value to upstreams list. Which upstream resources to forward
+          traffic to.
+
+           egressPolicy
+              Routing policy information.
+
+               regions
+                  List of the regions where the application sends traffic.
+
+           network
+              Network to forward traffic to.
+
+               name
+                  Network name is of the format:
+                  projects/{project}/global/networks/{network}.
+
+          Shorthand Example:
+
+              --add-upstreams=egressPolicy={regions=[string]},network={name=string} --add-upstreams=egressPolicy={regions=[string]},network={name=string}
+
+          JSON Example:
+
+              --add-upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]'
+
+          File Example:
+
+              --add-upstreams=path_to_file.(yaml|json)
+
+       At most one of these can be specified:
+
+         --clear-upstreams
+            Clear upstreams value and set to empty list.
+
+         --remove-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]
+            Remove existing value from upstreams list. Which upstream resources
+            to forward traffic to.
+
+             egressPolicy
+                Routing policy information.
+
+                 regions
+                    List of the regions where the application sends traffic.
+
+             network
+                Network to forward traffic to.
+
+                 name
+                    Network name is of the format:
+                    projects/{project}/global/networks/{network}.
+
+            Shorthand Example:
+
+                --remove-upstreams=egressPolicy={regions=[string]},network={name=string} --remove-upstreams=egressPolicy={regions=[string]},network={name=string}
+
+            JSON Example:
+
+                --remove-upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]'
+
+            File Example:
+
+                --remove-upstreams=path_to_file.(yaml|json)
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/create

@@ -0,0 +1,102 @@
+NAME
+    gcloud beta beyondcorp security-gateways create - create securityGateways
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways create
+        (SECURITY_GATEWAY : --location=LOCATION) [--async]
+        [--display-name=DISPLAY_NAME] [--hubs=[HUBS,...]]
+        [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create a securityGateway
+
+EXAMPLES
+    To create the securityGateway, run:
+
+        $ gcloud beta beyondcorp security-gateways create
+
+POSITIONAL ARGUMENTS
+     SecurityGateway resource - Identifier. Name of the resource. 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 security_gateway on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SECURITY_GATEWAY
+          ID of the securityGateway or fully qualified identifier for the
+          securityGateway.
+
+          To set the security_gateway attribute:
+          ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only
+          global location.
+
+          To set the location attribute:
+          ▸ provide the argument security_gateway on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        An arbitrary user-provided name for the SecurityGateway. Cannot exceed
+        64 characters.
+
+     --hubs=[HUBS,...]
+        Map of Hubs that represents regional data path deployment with Google
+        Cloud Platform region as a key.
+
+         KEY
+            Sets KEY value.
+
+         VALUE
+            Sets VALUE value.
+
+        Shorthand Example:
+
+            --hubs=string
+
+        JSON Example:
+
+            --hubs='{"string": {}}'
+
+        File Example:
+
+            --hubs=path_to_file.(yaml|json)
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore request if it has already been completed. The server will
+        guarantee that for at least 60 minutes since the first request.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/delete

@@ -0,0 +1,89 @@
+NAME
+    gcloud beta beyondcorp security-gateways delete - delete securityGateways
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways delete
+        (SECURITY_GATEWAY : --location=LOCATION) [--async]
+        [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Delete a securityGateway
+
+EXAMPLES
+    To delete the securityGateway, run:
+
+        $ gcloud beta beyondcorp security-gateways delete
+
+POSITIONAL ARGUMENTS
+     SecurityGateway resource - BeyondCorp SecurityGateway name using the form:
+     projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id}
+     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 security_gateway on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SECURITY_GATEWAY
+          ID of the securityGateway or fully qualified identifier for the
+          securityGateway.
+
+          To set the security_gateway attribute:
+          ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only
+          global location.
+
+          To set the location attribute:
+          ▸ provide the argument security_gateway on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore the request if it has already been completed. The server will
+        guarantee that for at least 60 minutes after the first request.
+
+        For example, consider a situation where you make an initial request and
+        the request times out. If you make the request again with the same
+        request ID, the server can check if original operation with the same
+        request ID was received, and if so, will ignore the second request.
+        This prevents clients from accidentally creating duplicate commitments.
+
+        The request ID must be a valid UUID with the exception that zero UUID
+        is not supported (00000000-0000-0000-0000-000000000000).
+
+     --validate-only
+        If set, validates request by executing a dry-run which would not alter
+        the resource in any way.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/describe

@@ -0,0 +1,66 @@
+NAME
+    gcloud beta beyondcorp security-gateways describe - describe
+        securityGateways
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways describe
+        (SECURITY_GATEWAY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Describe a securityGateway
+
+EXAMPLES
+    To describe the securityGateway, run:
+
+        $ gcloud beta beyondcorp security-gateways describe
+
+POSITIONAL ARGUMENTS
+     SecurityGateway resource - The resource name of the PartnerTenant using
+     the form:
+     projects/{project_id}/locations/{location_id}/securityGateway/{security_gateway_id}
+     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 security_gateway on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SECURITY_GATEWAY
+          ID of the securityGateway or fully qualified identifier for the
+          securityGateway.
+
+          To set the security_gateway attribute:
+          ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only
+          global location.
+
+          To set the location attribute:
+          ▸ provide the argument security_gateway on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/help

@@ -0,0 +1,43 @@
+NAME
+    gcloud beta beyondcorp security-gateways - manage Security Gateway
+        resources
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways GROUP | COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Manage Security Gateway resources.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+GROUPS
+    GROUP is one of the following:
+
+     applications
+        (BETA) Manage Application resources.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (BETA) Create securityGateways.
+
+     delete
+        (BETA) Delete securityGateways.
+
+     describe
+        (BETA) Describe securityGateways.
+
+     list
+        (BETA) List securityGateways.
+
+     update
+        (BETA) Update securityGateways.
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/list

@@ -0,0 +1,85 @@
+NAME
+    gcloud beta beyondcorp security-gateways list - list securityGateways
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways list --location=LOCATION
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) List securityGateways
+
+EXAMPLES
+    To list all securityGateways, run:
+
+        $ gcloud beta beyondcorp security-gateways list
+
+REQUIRED FLAGS
+     Location resource - The parent location to which the resources belong. We
+     support only global location.
+
+     projects/{project_id}/locations/{location_id}/ This represents a Cloud
+     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 --location on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       --location=LOCATION
+          ID of the location or fully qualified identifier for the location.
+
+          To set the location attribute:
+          ▸ provide the argument --location on the command line.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+

gcloud/beta/beyondcorp/security-gateways/update

@@ -0,0 +1,159 @@
+NAME
+    gcloud beta beyondcorp security-gateways update - update securityGateways
+
+SYNOPSIS
+    gcloud beta beyondcorp security-gateways update
+        (SECURITY_GATEWAY : --location=LOCATION) [--async]
+        [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID]
+        [--hubs=[HUBS,...] | --update-hubs=[UPDATE_HUBS,...] --clear-hubs
+          | --remove-hubs=REMOVE_HUBS] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Update a securityGateway
+
+EXAMPLES
+    To update the securityGateway, run:
+
+        $ gcloud beta beyondcorp security-gateways update
+
+POSITIONAL ARGUMENTS
+     SecurityGateway resource - Identifier. Name of the resource. 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 security_gateway on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       SECURITY_GATEWAY
+          ID of the securityGateway or fully qualified identifier for the
+          securityGateway.
+
+          To set the security_gateway attribute:
+          ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only
+          global location.
+
+          To set the location attribute:
+          ▸ provide the argument security_gateway on the command line with a
+            fully specified name;
+          ▸ provide the argument --location on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --display-name=DISPLAY_NAME
+        An arbitrary user-provided name for the SecurityGateway. Cannot exceed
+        64 characters.
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore the request if it has already been completed. The server will
+        guarantee that for at least 60 minutes after the first request.
+
+        For example, consider a situation where you make an initial request and
+        the request timed out. If you make the request again with the same
+        request ID, the server can check if original operation with the same
+        request ID was received, and if so, will ignore the second request.
+        This prevents clients from accidentally creating duplicate commitments.
+
+        The request ID must be a valid UUID with the exception that zero UUID
+        is not supported (00000000-0000-0000-0000-000000000000).
+
+     Update hubs.
+
+     At most one of these can be specified:
+
+       --hubs=[HUBS,...]
+          Set hubs to new value. Map of Hubs that represents regional data path
+          deployment with Google Cloud Platform region as a key.
+
+           KEY
+              Sets KEY value.
+
+           VALUE
+              Sets VALUE value.
+
+          Shorthand Example:
+
+              --hubs=string
+
+          JSON Example:
+
+              --hubs='{"string": {}}'
+
+          File Example:
+
+              --hubs=path_to_file.(yaml|json)
+
+       --update-hubs=[UPDATE_HUBS,...]
+          Update hubs value or add key value pair. Map of Hubs that represents
+          regional data path deployment with Google Cloud Platform region as a
+          key.
+
+           KEY
+              Sets KEY value.
+
+           VALUE
+              Sets VALUE value.
+
+          Shorthand Example:
+
+              --update-hubs=string
+
+          JSON Example:
+
+              --update-hubs='{"string": {}}'
+
+          File Example:
+
+              --update-hubs=path_to_file.(yaml|json)
+
+       At most one of these can be specified:
+
+         --clear-hubs
+            Clear hubs value and set to empty map.
+
+         --remove-hubs=REMOVE_HUBS
+            Remove existing value from map hubs. Sets remove_hubs value.
+
+            Shorthand Example:
+
+                --remove-hubs=string,string
+
+            JSON Example:
+
+                --remove-hubs=["string"]
+
+            File Example:
+
+                --remove-hubs=path_to_file.(yaml|json)
+
+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/v1 API. The full documentation for this
+    API can be found at: https://cloud.google.com/
+
+NOTES
+    This command is currently in beta and might change without notice.
+