gcloud: Wed Dec 10 10:54:29 UTC 2025

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

@@ -5,9 +5,9 @@ NAME
 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]
-        [--schema=SCHEMA]
+        [--async] [--display-name=DISPLAY_NAME]
+        [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]]
+        [--request-id=REQUEST_ID] [--schema=SCHEMA]
         [--upstreams=[egressPolicy=EGRESSPOLICY],
           [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]]
         [GCLOUD_WIDE_FLAG ...]
@@ -61,23 +61,33 @@ POSITIONAL ARGUMENTS
             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
-        should be the following combination: (Hostname & Ports)
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
 
-        EXAMPLES: Hostname and Ports - (".example.com", "443"), ("example.com"
-        and "22"), ("example.com" and "22,33") etc.
+     --display-name=DISPLAY_NAME
+        An arbitrary user-provided name for the application resource. Cannot
+        exceed 64 characters.
+
+     --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]
+        An array of conditions to match the application's network endpoint.
+        Each element in the array is an EndpointMatcher object, which defines a
+        specific combination of a hostname pattern and one or more ports. The
+        application is considered matched if at least one of the
+        EndpointMatcher conditions in this array is met (the conditions are
+        combined using OR logic). Each EndpointMatcher must contain a hostname
+        pattern, such as "example.com", and one or more port numbers specified
+        as a string, such as "443".
+
+        Hostname and port number examples: ".example.com", "443" "example.com"
+        and "22" "example.com" and "22,33".
 
          hostname
             Hostname of the application.
 
          ports
-            Ports of the application.
+            The ports of the application.
 
         Shorthand Example:
 
@@ -91,15 +101,6 @@ REQUIRED FLAGS
 
             --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
@@ -158,35 +159,35 @@ OPTIONAL FLAGS
                 Configuration for the contextual headers.
 
                  deviceInfo
-                    Device info configuration.
+                    The device information configuration.
 
                      outputType
-                        The output type of the delegated device info.
+                        The output type details for the delegated device.
 
                  groupInfo
-                    Group info configuration.
+                    Group details.
 
                      outputType
-                        The output type of the delegated group info.
+                        The output type of the delegated group information.
 
                  outputType
                     Default output type for all enabled headers.
 
                  userInfo
-                    User info configuration.
+                    User details.
 
                      outputType
-                        The output type of the delegated user info.
+                        The delegated user's information.
 
              gatewayIdentity
-                Gateway identity configuration.
+                The security gateway identity configuration.
 
              metadataHeaders
                 Custom resource specific headers along with the values. The
-                names should conform to RFC 9110: > Field names SHOULD
-                constrain themselves to alphanumeric characters, "-", and ".",
-                and SHOULD begin with a letter. Field values SHOULD contain
-                only ASCII printable characters and tab.
+                names should conform to RFC 9110: >Field names can contain
+                alphanumeric characters, hyphens, and periods, can contain only
+                ASCII-printable characters and tabs, and must start with a
+                letter.
 
                  KEY
                     Sets KEY value.
@@ -219,5 +220,8 @@ API REFERENCE
     API can be found at: https://cloud.google.com/
 
 NOTES
-    This command is currently in beta and might change without notice.
+    This command is currently in beta and might change without notice. This
+    variant is also available:
+
+        $ gcloud beyondcorp security-gateways applications create