gcloud: Wed Nov 15 11:42:54 UTC 2023

gcloud/functions/deploy

@@ -3,10 +3,10 @@ NAME
 
 SYNOPSIS
     gcloud functions deploy (NAME : --region=REGION)
-        [--[no-]allow-unauthenticated] [--docker-registry=DOCKER_REGISTRY]
-        [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT]
-        [--gen2] [--ignore-file=IGNORE_FILE]
-        [--ingress-settings=INGRESS_SETTINGS] [--memory=MEMORY] [--retry]
+        [--[no-]allow-unauthenticated] [--concurrency=CONCURRENCY]
+        [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS]
+        [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE]
+        [--ingress-settings=INGRESS_SETTINGS] [--retry]
         [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME]
         [--security-level=SECURITY_LEVEL; default="secure-always"]
         [--serve-all-traffic-latest-revision]
@@ -38,6 +38,7 @@ SYNOPSIS
           /secret_path=SECRET_VALUE_REF,
           /mount_path:/secret_file_path=SECRET_VALUE_REF,...]]
         [--clear-vpc-connector | --vpc-connector=VPC_CONNECTOR]
+        [--memory=MEMORY : --cpu=CPU]
         [--trigger-bucket=TRIGGER_BUCKET | --trigger-http
           | --trigger-topic=TRIGGER_TOPIC
           | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE
@@ -100,6 +101,11 @@ FLAGS
         without checking authentication. Use --allow-unauthenticated to enable
         and --no-allow-unauthenticated to disable.
 
+     --concurrency=CONCURRENCY
+        Set the maximum number of concurrent requests allowed per container
+        instance. Leave concurrency unspecified to receive the server default
+        value. Only applicable when the --gen2 flag is provided.
+
      --docker-registry=DOCKER_REGISTRY
         Docker Registry to use for storing the function's Docker images. The
         option container-registry is used by default.
@@ -136,22 +142,6 @@ FLAGS
         default all will be used. INGRESS_SETTINGS must be one of: all,
         internal-only, internal-and-gclb.
 
-     --memory=MEMORY
-        Limit on the amount of memory the function can use.
-
-        Allowed values for v1 are: 128MB, 256MB, 512MB, 1024MB, 2048MB, 4096MB,
-        and 8192MB.
-
-        Allowed values for GCF 2nd gen are in the format: <number><unit> with
-        allowed units of "k", "M", "G", "Ki", "Mi", "Gi". Ending 'b' or 'B' is
-        allowed.
-
-        Examples: 100000k, 128M, 10Mb, 1024Mi, 750K, 4Gi.
-
-        By default, a new function is limited to 256MB of memory. When
-        deploying an update to an existing function, the function keeps its old
-        memory limit unless you specify this flag.
-
      --retry
         If specified, then the function will be retried in case of a failure.
 
@@ -553,6 +543,38 @@ FLAGS
             To set the connector attribute:
             ▫ provide the argument --vpc-connector on the command line.
 
+     --memory=MEMORY
+        Limit on the amount of memory the function can use.
+
+        Allowed values for v1 are: 128MB, 256MB, 512MB, 1024MB, 2048MB, 4096MB,
+        and 8192MB.
+
+        Allowed values for GCF 2nd gen are in the format: <number><unit> with
+        allowed units of "k", "M", "G", "Ki", "Mi", "Gi". Ending 'b' or 'B' is
+        allowed.
+
+        Examples: 100000k, 128M, 10Mb, 1024Mi, 750K, 4Gi.
+
+        By default, a new function is limited to 256MB of memory. When
+        deploying an update to an existing function, the function keeps its old
+        memory limit unless you specify this flag.
+
+     --cpu=CPU
+        The number of available CPUs to set. Only valid when --gen2 and
+        --memory=MEMORY are specified.
+
+        Examples: .5, 2, 2.0, 2000m.
+
+        By default, a new function's available CPUs is determined based on its
+        memory value.
+
+        When deploying an update that includes memory changes to an existing
+        function, the function's available CPUs will be recalculated based on
+        the new memory unless this flag is specified. When deploying an update
+        that does not include memory changes to an existing function, the
+        function's "available CPUs" setting will keep its old value unless you
+        use this flag to change the setting.
+
      If you don't specify a trigger when deploying an update to an existing
      function it will keep its current trigger. You must specify one of the
      following when deploying a new function: