imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 06:47:12 +00:00
Code Activity

gcloud: Fri Jun 2 10:25:45 UTC 2023

Browse source
This commit is contained in:
Automated 2023-06-02 10:25:45 +00:00
parent d0919dce4f
commit daa9cea776
199 changed files with 7828 additions and 401 deletions
Download patch file Download diff file Expand all files Collapse all files

17
gcloud/compute/backend-buckets/update
View file

@ -172,7 +172,11 @@ FLAGS
this field.
--no-client-ttl
Clears client TTL value.
(DEPRECATED) Clears client TTL value.
The --no-client-ttl option is deprecated and will be removed in an
upcoming release. If you're currently using this argument, you should
remove it from your workflows.
At most one of these can be specified:
@ -244,7 +248,11 @@ FLAGS
omit this field.
--no-max-ttl
Clears max TTL value.
(DEPRECATED) Clears max TTL value.
The --no-max-ttl option is deprecated and will be removed in an
upcoming release. If you're currently using this argument, you should
remove it from your workflows.
At most one of these can be specified:
@ -333,9 +341,8 @@ FLAGS
(DEPRECATED) Clears serve while stale value.
The --no-serve-while-stale option is deprecated and will be removed
in an upcoming release; use --serve-while-stale instead. If you're
currently using this argument, you should remove it from your
workflows.
in an upcoming release. If you're currently using this argument, you
should remove it from your workflows.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

17
gcloud/compute/backend-services/update
View file

@ -525,7 +525,11 @@ FLAGS
this field.
--no-client-ttl
Clears client TTL value.
(DEPRECATED) Clears client TTL value.
The --no-client-ttl option is deprecated and will be removed in an
upcoming release. If you're currently using this argument, you should
remove it from your workflows.
At most one of these can be specified:
@ -644,7 +648,11 @@ FLAGS
omit this field.
--no-max-ttl
Clears max TTL value.
(DEPRECATED) Clears max TTL value.
The --no-max-ttl option is deprecated and will be removed in an
upcoming release. If you're currently using this argument, you should
remove it from your workflows.
At most one of these can be specified:
@ -733,9 +741,8 @@ FLAGS
(DEPRECATED) Clears serve while stale value.
The --no-serve-while-stale option is deprecated and will be removed
in an upcoming release; use --serve-while-stale instead. If you're
currently using this argument, you should remove it from your
workflows.
in an upcoming release. If you're currently using this argument, you
should remove it from your workflows.
At most one of these can be specified:

18
gcloud/compute/instance-groups/managed/set-autoscaling
View file

@ -46,12 +46,18 @@ REQUIRED FLAGS
OPTIONAL FLAGS
--cool-down-period=COOL_DOWN_PERIOD
The time period that the autoscaler should wait before it starts
collecting information from a new instance. This prevents the
autoscaler from collecting information when the instance is
initializing, during which the collected usage would not be reliable.
The default is 60s. See $ gcloud topic datetimes for information on
duration formats.
The number of seconds that your application takes to initialize on a VM
instance. This is referred to as the initialization period
(https://cloud.google.com/compute/docs/autoscaler#cool_down_period).
Specifying an accurate initialization period improves autoscaler
decisions. For example, when scaling out, the autoscaler ignores data
from VMs that are still initializing because those VMs might not yet
represent normal usage of your application. The default initialization
period is 60 seconds. See $ gcloud topic datetimes for information on
duration formats. Initialization periods might vary because of numerous
factors. We recommend that you test how long your application may take
to initialize. To do this, create a VM and time your application's
startup process.
--cpu-utilization-predictive-method=CPU_UTILIZATION_PREDICTIVE_METHOD
Indicates whether to use a predictive algorithm when scaling based on

16
gcloud/compute/service-attachments/create
View file

@ -13,7 +13,7 @@ SYNOPSIS
[--domain-names=[DOMAIN_NAMES,...]] [--enable-proxy-protocol]
[--nat-subnets-region=NAT_SUBNETS_REGION]
[--producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION]
[--region=REGION] [GCLOUD_WIDE_FLAG ...]
[--reconcile-connections] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute service-attachments create is used to create service
@ -127,6 +127,20 @@ OPTIONAL FLAGS
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
--reconcile-connections
Determines whether to apply changes to consumer accept or reject lists
to existing connections or only to new connections.
If false, existing endpoints with a connection status of ACCEPTED or
REJECTED are not updated.
If true, existing endpoints with a connection status of ACCEPTED or
REJECTED are updated based on the connection policy update. For
example, if a project or network is removed from the
--consumer-accept-list and added to --consumer-reject-list, all the
endpoints in that project or network with the ACCEPTED state are set to
REJECTED.
--region=REGION
Region of the service attachment to create. If not specified, you might
be prompted to select a region (interactive mode only).

21
gcloud/compute/service-attachments/update
View file

@ -9,8 +9,8 @@ SYNOPSIS
[--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION]
[--[no-]enable-proxy-protocol]
[--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...]]
[--nat-subnets-region=NAT_SUBNETS_REGION] [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
[--nat-subnets-region=NAT_SUBNETS_REGION]
[--[no-]reconcile-connections] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute service-attachments update is used to update service
@ -93,6 +93,23 @@ FLAGS
set to the region of the service attachment. Overrides the default
compute/region property value for this command invocation.
--[no-]reconcile-connections
Determines whether to apply changes to consumer accept or reject lists
to existing connections or only to new connections.
If false, existing endpoints with a connection status of ACCEPTED or
REJECTED are not updated.
If true, existing endpoints with a connection status of ACCEPTED or
REJECTED are updated based on the connection policy update. For
example, if a project or network is removed from the
--consumer-accept-list and added to --consumer-reject-list, all the
endpoints in that project or network with the ACCEPTED state are set to
REJECTED.
Use --reconcile-connections to enable and --no-reconcile-connections to
disable.
--region=REGION
Region of the service attachment to update. If not specified, you might
be prompted to select a region (interactive mode only).