imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Mon Oct 23 11:10:08 UTC 2023

Browse source
This commit is contained in:
Automated 2023-10-23 11:10:09 +00:00
parent c30bb7b4ce
commit a15665661a
123 changed files with 3724 additions and 306 deletions
Download patch file Download diff file Expand all files Collapse all files

14
gcloud/alpha/compute/backend-services/create
View file

@ -339,8 +339,8 @@ FLAGS
as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies preference of traffic to the backend (from the proxy and from
the client for proxyless gRPC).
Specifies a preference for traffic sent from the proxy to the backend
(or from the client to the backend for proxyless gRPC).
Can only be set if load balancing scheme is INTERNAL_SELF_MANAGED,
INTERNAL_MANAGED or EXTERNAL_MANAGED.
@ -348,18 +348,18 @@ FLAGS
The possible values are:
IPV4_ONLY
Only send IPv4 traffic to the backends of the Backend Service
Only send IPv4 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv4
health-checks are used to check the health of the backends.
health checks are used to check the health of the backends.
PREFER_IPV6
Prioritize the connection to the endpoints IPv6 address over its IPv4
Prioritize the connection to the endpoint's IPv6 address over its IPv4
address (provided there is a healthy IPv6 address).
IPV6_ONLY
Only send IPv6 traffic to the backends of the Backend Service
Only send IPv6 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv6
health-checks are used to check the health of the backends.
health checks are used to check the health of the backends.
IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6,
IPV6_ONLY.

6
gcloud/alpha/compute/backend-services/list-usable
View file

@ -9,7 +9,7 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) $ gcloud alpha compute backend-services list-usable retrieves the
(ALPHA) gcloud alpha compute backend-services list-usable retrieves the
list of backend service resources in the specified project for which you
have compute.backendService.get and compute.backendService.use permissions.
This command is useful when you're creating load balancers in a Shared VPC
@ -85,7 +85,9 @@ 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:
access allowlist. These variants are also available:
$ gcloud compute backend-services list-usable
$ gcloud beta compute backend-services list-usable

14
gcloud/alpha/compute/backend-services/update
View file

@ -258,8 +258,8 @@ FLAGS
as part of a connection tracking policy.
--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY
Specifies preference of traffic to the backend (from the proxy and from
the client for proxyless gRPC).
Specifies a preference for traffic sent from the proxy to the backend
(or from the client to the backend for proxyless gRPC).
Can only be set if load balancing scheme is INTERNAL_SELF_MANAGED,
INTERNAL_MANAGED or EXTERNAL_MANAGED.
@ -267,18 +267,18 @@ FLAGS
The possible values are:
IPV4_ONLY
Only send IPv4 traffic to the backends of the Backend Service
Only send IPv4 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv4
health-checks are used to check the health of the backends.
health checks are used to check the health of the backends.
PREFER_IPV6
Prioritize the connection to the endpoints IPv6 address over its IPv4
Prioritize the connection to the endpoint's IPv6 address over its IPv4
address (provided there is a healthy IPv6 address).
IPV6_ONLY
Only send IPv6 traffic to the backends of the Backend Service
Only send IPv6 traffic to the backends of the backend service,
regardless of traffic from the client to the proxy. Only IPv6
health-checks are used to check the health of the backends.
health checks are used to check the health of the backends.
IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6,
IPV6_ONLY.

3
gcloud/alpha/compute/network-attachments/help
View file

@ -28,6 +28,9 @@ COMMANDS
list
(ALPHA) List Google Compute Engine network attachments.
update
(ALPHA) Update a Google Compute Engine network attachment.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct

72
gcloud/alpha/compute/network-attachments/update Normal file
View file

@ -0,0 +1,72 @@
NAME
gcloud alpha compute network-attachments update - update a Google Compute
Engine network attachment
SYNOPSIS
gcloud alpha compute network-attachments update NAME
[--description=DESCRIPTION] [--producer-accept-list=[ACCEPT_LIST,...]]
[--producer-reject-list=[REJECT_LIST,...]] [--region=REGION]
[--subnets=SUBNETS,[SUBNETS,...]] [--subnets-region=SUBNETS_REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) gcloud alpha compute network-attachments update is used to update
network attachments. A service consumer creates a network attachment to
make a network available to producers. Service producers use Private
Service Connect Interfaces to privately connect to the network attachment.
POSITIONAL ARGUMENTS
NAME
Name of the network attachment to update.
FLAGS
--description=DESCRIPTION
An optional, textual description for the network attachment.
--producer-accept-list=[ACCEPT_LIST,...]
Projects that are allowed to connect to this network attachment.
--producer-reject-list=[REJECT_LIST,...]
Projects that are not allowed to connect to this network attachment.
--region=REGION
Region of the network attachment to update. If not specified, you might
be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
--subnets=SUBNETS,[SUBNETS,...]
The subnetworks provided by the consumer for the producers
--subnets-region=SUBNETS_REGION
Region of the subnetworks to operate on. Overrides the default
compute/region property value for this command invocation.
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.
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.

10
gcloud/alpha/compute/sole-tenancy/node-groups/create
View file

@ -43,12 +43,14 @@ OPTIONAL FLAGS
MAINTENANCE_INTERVAL must be one of:
as-needed
VMs are eligible to receive infrastructure and hypervisor updates
hosts are eligible to receive infrastructure and hypervisor updates
as they become available.
recurrent
VMs receive infrastructure and hypervisor updates on a periodic
basis, minimizing the number of maintenance operations (live
migrations or terminations) on an individual VM.
hosts receive planned infrastructure and hypervisor updates on a
periodic basis, but not more frequently than every 28 days. This
minimizes the number of planned maintenance operations on
individual hosts and reduces the frequency of disruptions, both
live migrations and terminations, on individual VMs.
--maintenance-policy=MAINTENANCE_POLICY
Determines the maintenance behavior during host maintenance events. For