mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-20 21:20:07 +00:00
gcloud: Wed Jul 27 08:55:33 UTC 2022
This commit is contained in:
Automated
parent
380c3aa29f
commit
3513fd1c11
171 changed files with 3989 additions and 448 deletions
|
|
@ -18,7 +18,7 @@ SYNOPSIS
|
|||
[--smooth-grad-noise-sigma=SMOOTH_GRAD_NOISE_SIGMA]
|
||||
[--smooth-grad-noise-sigma-by-feature=[KEY=VALUE,...]]
|
||||
[--smooth-grad-noisy-sample-count=SMOOTH_GRAD_NOISY_SAMPLE_COUNT]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
[--version-aliases=[VERSION_ALIASES,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
EXAMPLES
|
||||
To upload a model under project example in region us-central1, run:
|
||||
|
|
@ -123,6 +123,11 @@ OPTIONAL FLAGS
|
|||
Number of gradient samples used for approximation at explanation. Only
|
||||
applicable to explanation method integrated-gradients or xrai.
|
||||
|
||||
--version-aliases=[VERSION_ALIASES,...]
|
||||
Aliases used to reference a model version instead of auto-generated
|
||||
version ID. The aliases mentioned in the flag will replace the aliases
|
||||
set in the model.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -3,9 +3,9 @@ NAME
|
|||
instances
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha anthos config controller list [--location=LOCATION]
|
||||
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
|
||||
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
gcloud alpha anthos config controller list [--full-name]
|
||||
[--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT]
|
||||
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) List Anthos Config Controller instances.
|
||||
|
|
@ -16,11 +16,19 @@ EXAMPLES
|
|||
|
||||
$ gcloud alpha anthos config controller list --location=us-central1
|
||||
|
||||
To list all Anthos Config Controller instances in all regions with their
|
||||
fully specified name, run:
|
||||
|
||||
$ gcloud alpha anthos config controller list --full-name
|
||||
|
||||
To list all Anthos Config Controller instances in all regions, run:
|
||||
|
||||
$ gcloud alpha anthos config controller list
|
||||
|
||||
FLAGS
|
||||
--full-name
|
||||
Print the fully specified name of the instance.
|
||||
|
||||
Instance list resource - List of Anthos Config Controller instances. 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
|
||||
|
|
|
|||
|
|
@ -125,5 +125,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections create
|
||||
|
||||
|
|
|
|||
|
|
@ -63,5 +63,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections delete
|
||||
|
||||
|
|
|
|||
|
|
@ -68,5 +68,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections describe
|
||||
|
||||
|
|
|
|||
|
|
@ -38,5 +38,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections
|
||||
|
||||
|
|
|
|||
|
|
@ -84,5 +84,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections list
|
||||
|
||||
|
|
|
|||
|
|
@ -113,5 +113,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connections update
|
||||
|
||||
|
|
|
|||
|
|
@ -94,5 +94,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors create
|
||||
|
||||
|
|
|
|||
|
|
@ -63,5 +63,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors delete
|
||||
|
||||
|
|
|
|||
|
|
@ -71,5 +71,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors describe
|
||||
|
||||
|
|
|
|||
|
|
@ -39,5 +39,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors
|
||||
|
||||
|
|
|
|||
|
|
@ -83,5 +83,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors list
|
||||
|
||||
|
|
|
|||
|
|
@ -102,5 +102,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app connectors update
|
||||
|
||||
|
|
|
|||
|
|
@ -43,5 +43,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app
|
||||
|
||||
|
|
|
|||
|
|
@ -63,5 +63,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app operations describe
|
||||
|
||||
|
|
|
|||
|
|
@ -26,5 +26,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app operations
|
||||
|
||||
|
|
|
|||
|
|
@ -78,5 +78,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp app operations list
|
||||
|
||||
|
|
|
|||
|
|
@ -84,5 +84,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector gateways create
|
||||
|
||||
|
|
|
|||
|
|
@ -65,5 +65,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector gateways delete
|
||||
|
||||
|
|
|
|||
|
|
@ -61,5 +61,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector gateways describe
|
||||
|
||||
|
|
|
|||
|
|
@ -38,5 +38,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector gateways
|
||||
|
||||
|
|
|
|||
|
|
@ -77,5 +77,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector gateways list
|
||||
|
||||
|
|
|
|||
|
|
@ -40,5 +40,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector
|
||||
|
||||
|
|
|
|||
|
|
@ -63,5 +63,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector operations describe
|
||||
|
||||
|
|
|
|||
|
|
@ -27,5 +27,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector operations
|
||||
|
||||
|
|
|
|||
|
|
@ -78,5 +78,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector operations list
|
||||
|
||||
|
|
|
|||
|
|
@ -135,5 +135,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services create
|
||||
|
||||
|
|
|
|||
|
|
@ -69,5 +69,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services delete
|
||||
|
||||
|
|
|
|||
|
|
@ -63,5 +63,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services describe
|
||||
|
||||
|
|
|
|||
|
|
@ -43,5 +43,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services
|
||||
|
||||
|
|
|
|||
|
|
@ -83,5 +83,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services list
|
||||
|
||||
|
|
|
|||
|
|
@ -77,5 +77,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp client-connector services update
|
||||
|
||||
|
|
|
|||
|
|
@ -37,5 +37,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta beyondcorp
|
||||
|
||||
|
|
|
|||
|
|
@ -86,8 +86,8 @@ FLAGS
|
|||
https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features
|
||||
for descriptions of the supported features. GUEST_OS_FEATURE must be
|
||||
one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, MULTI_IP_SUBNET,
|
||||
SEV_CAPABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE,
|
||||
WINDOWS.
|
||||
SEV_CAPABLE, SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE,
|
||||
VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
|
||||
|
||||
--interface=INTERFACE
|
||||
Specifies the disk interface to use for attaching this disk. Valid
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ POSITIONAL ARGUMENTS
|
|||
REQUIRED FLAGS
|
||||
--action=ACTION
|
||||
Action to take if the request matches the match condition. ACTION must
|
||||
be one of: allow, deny, goto_next, apply_profile_group.
|
||||
be one of: allow, deny, goto_next, apply_security_profile_group.
|
||||
|
||||
--firewall-policy=FIREWALL_POLICY
|
||||
Short name of the firewall policy into which the rule should be
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ REQUIRED FLAGS
|
|||
OPTIONAL FLAGS
|
||||
--action=ACTION
|
||||
Action to take if the request matches the match condition. ACTION must
|
||||
be one of: allow, deny, goto_next, apply_profile_group.
|
||||
be one of: allow, deny, goto_next, apply_security_profile_group.
|
||||
|
||||
--description=DESCRIPTION
|
||||
An optional, textual description for the rule.
|
||||
|
|
|
|||
|
|
@ -152,8 +152,8 @@ OPTIONAL FLAGS
|
|||
https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features
|
||||
for descriptions of the supported features. GUEST_OS_FEATURE must be
|
||||
one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, MULTI_IP_SUBNET,
|
||||
SEV_CAPABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE,
|
||||
WINDOWS.
|
||||
SEV_CAPABLE, SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE,
|
||||
VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
|
||||
|
||||
--key-exchange-key-file=[KEK_VALUE,...]
|
||||
Comma-separated list of file paths that point to X.509 certificates in
|
||||
|
|
|
|||
|
|
@ -5,7 +5,9 @@ SYNOPSIS
|
|||
gcloud alpha compute images update IMAGE_NAME [--architecture=ARCHITECTURE]
|
||||
[--description=DESCRIPTION] [--family=FAMILY]
|
||||
[--update-labels=[KEY=VALUE,...]]
|
||||
[--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
[--clear-labels | --remove-labels=[KEY,...]]
|
||||
[--clear-user-licenses | --update-user-licenses=[LICENSE,...]]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute images update updates labels for a Compute
|
||||
|
|
@ -75,6 +77,16 @@ FLAGS
|
|||
silently ignored. If --update-labels is also specified then
|
||||
--update-labels is applied first.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-user-licenses
|
||||
Remove all existing user licenses on an image.
|
||||
|
||||
--update-user-licenses=[LICENSE,...]
|
||||
List of user licenses to be updated on an image. These user licenses
|
||||
replace all existing user licenses. If this flag is not provided, all
|
||||
existing user licenses remain unchanged.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -65,8 +65,8 @@ SYNOPSIS
|
|||
[exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES],
|
||||
[exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES],
|
||||
[mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER],
|
||||
[proxy-port=PROXY-PORT],
|
||||
[scope=SCOPE],[serving-ports=SERVING-PORTS],[tracing=TRACING]
|
||||
[proxy-port=PROXY-PORT],[scope=SCOPE],
|
||||
[serving-ports=SERVING-PORTS],[source=SOURCE],[tracing=TRACING]
|
||||
--service-proxy-labels=[KEY=VALUE, ...,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -1056,7 +1056,7 @@ FLAGS
|
|||
--no-service-account
|
||||
Create instance without service account
|
||||
|
||||
--service-proxy=[enabled],[intercept-all-outbound-traffic],[intercept-dns],[access-log=ACCESS-LOG],[exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES],[exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES],[mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER],[proxy-port=PROXY-PORT],[scope=SCOPE],[serving-ports=SERVING-PORTS],[tracing=TRACING]
|
||||
--service-proxy=[enabled],[intercept-all-outbound-traffic],[intercept-dns],[access-log=ACCESS-LOG],[exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES],[exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES],[mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER],[proxy-port=PROXY-PORT],[scope=SCOPE],[serving-ports=SERVING-PORTS],[source=SOURCE],[tracing=TRACING]
|
||||
Controls whether the Traffic Director service proxy (Envoy) and agent
|
||||
are installed and configured on the VM. "cloud-platform" scope is
|
||||
enabled automatically to allow connections to the Traffic Director API.
|
||||
|
|
@ -1106,6 +1106,15 @@ FLAGS
|
|||
intercept-dns
|
||||
Enables interception of UDP traffic by the service proxy.
|
||||
|
||||
source
|
||||
The Google Cloud Storage bucket location source for the Envoy. The
|
||||
service-proxy-agent will download the archive from Envoy and
|
||||
install it on the virtual machine, unpacking it into the root (/)
|
||||
directory of the virtual machine. Therefore, the archive must
|
||||
contain not only the executable and license files but they must be
|
||||
located in the correct directories within the archive. For example:
|
||||
/usr/local/bin/envoy and /usr/local/doc/envoy-LICENSE
|
||||
|
||||
intercept-all-outbound-traffic
|
||||
Enables interception of all outgoing traffic. The traffic is
|
||||
intercepted by the service proxy and then redirected to external
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ POSITIONAL ARGUMENTS
|
|||
REQUIRED FLAGS
|
||||
--action=ACTION
|
||||
Action to take if the request matches the match condition. ACTION must
|
||||
be one of: allow, deny, goto_next, apply_profile_group.
|
||||
be one of: allow, deny, goto_next, apply_security_profile_group.
|
||||
|
||||
--firewall-policy=FIREWALL_POLICY
|
||||
Firewall policy ID with which to create rule.
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ REQUIRED FLAGS
|
|||
OPTIONAL FLAGS
|
||||
--action=ACTION
|
||||
Action to take if the request matches the match condition. ACTION must
|
||||
be one of: allow, deny, goto_next, apply_profile_group.
|
||||
be one of: allow, deny, goto_next, apply_security_profile_group.
|
||||
|
||||
--description=DESCRIPTION
|
||||
An optional, textual description for the rule.
|
||||
|
|
|
|||
|
|
@ -24,6 +24,8 @@ DESCRIPTION
|
|||
|
||||
+ Checks if the VM Manager service agent is enabled.
|
||||
|
||||
+ Checks if the VM instance has a public IP or Private Google Access.
|
||||
|
||||
EXAMPLES
|
||||
To troubleshoot an instance named my-instance in zone us-west1-a, run
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,8 @@ SYNOPSIS
|
|||
[--enforce-on-key=ENFORCE_ON_KEY]
|
||||
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
|
||||
[--exceed-action=EXCEED_ACTION]
|
||||
[--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
|
||||
[--exceed-action-rpc-status-message=EXCEED_ACTION_RPC_STATUS_MESSAGE]
|
||||
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
|
||||
[--exceed-redirect-type=EXCEED_REDIRECT_TYPE] [--preview]
|
||||
[--rate-limit-threshold-count=RATE_LIMIT_THRESHOLD_COUNT]
|
||||
|
|
@ -58,6 +60,10 @@ REQUIRED FLAGS
|
|||
deny-502
|
||||
Denies the request from HTTP(S) Load Balancing, with an HTTP
|
||||
response status code of 503.
|
||||
fairshare
|
||||
When traffic reaches the threshold limit, requests from the clients
|
||||
matching this rule begin to be rate-limited using the Fair Share
|
||||
algorithm.
|
||||
rate-based-ban
|
||||
Enforces rate-based ban action from HTTP(S) Load Balancing, based
|
||||
on rate limit options.
|
||||
|
|
@ -144,6 +150,12 @@ OPTIONAL FLAGS
|
|||
EXCEED_ACTION must be one of: deny-403, deny-404, deny-429, deny-502,
|
||||
deny, redirect.
|
||||
|
||||
--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE
|
||||
Status code, which should be an enum value of [google.rpc.Code]
|
||||
|
||||
--exceed-action-rpc-status-message=EXCEED_ACTION_RPC_STATUS_MESSAGE
|
||||
Developer-facing error message, should be in English.
|
||||
|
||||
--exceed-redirect-target=EXCEED_REDIRECT_TARGET
|
||||
URL target for the redirect action that is configured as the exceed
|
||||
action when the redirect type is external-302.
|
||||
|
|
|
|||
|
|
@ -11,6 +11,8 @@ SYNOPSIS
|
|||
[--enforce-on-key=ENFORCE_ON_KEY]
|
||||
[--enforce-on-key-name=ENFORCE_ON_KEY_NAME]
|
||||
[--exceed-action=EXCEED_ACTION]
|
||||
[--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE]
|
||||
[--exceed-action-rpc-status-message=EXCEED_ACTION_RPC_STATUS_MESSAGE]
|
||||
[--exceed-redirect-target=EXCEED_REDIRECT_TARGET]
|
||||
[--exceed-redirect-type=EXCEED_REDIRECT_TYPE] [--preview]
|
||||
[--rate-limit-threshold-count=RATE_LIMIT_THRESHOLD_COUNT]
|
||||
|
|
@ -57,6 +59,10 @@ FLAGS
|
|||
deny-502
|
||||
Denies the request from HTTP(S) Load Balancing, with an HTTP
|
||||
response status code of 503.
|
||||
fairshare
|
||||
When traffic reaches the threshold limit, requests from the clients
|
||||
matching this rule begin to be rate-limited using the Fair Share
|
||||
algorithm.
|
||||
rate-based-ban
|
||||
Enforces rate-based ban action from HTTP(S) Load Balancing, based
|
||||
on rate limit options.
|
||||
|
|
@ -131,6 +137,12 @@ FLAGS
|
|||
EXCEED_ACTION must be one of: deny-403, deny-404, deny-429, deny-502,
|
||||
deny, redirect.
|
||||
|
||||
--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE
|
||||
Status code, which should be an enum value of [google.rpc.Code]
|
||||
|
||||
--exceed-action-rpc-status-message=EXCEED_ACTION_RPC_STATUS_MESSAGE
|
||||
Developer-facing error message, should be in English.
|
||||
|
||||
--exceed-redirect-target=EXCEED_REDIRECT_TARGET
|
||||
URL target for the redirect action that is configured as the exceed
|
||||
action when the redirect type is external-302.
|
||||
|
|
|
|||
|
|
@ -100,9 +100,8 @@ AVAILABLE PROPERTIES
|
|||
|
||||
disable_usage_reporting
|
||||
If True, anonymous statistics on SDK usage will not be collected.
|
||||
This value is set by default based on your choices during
|
||||
installation, but can be changed at any time. For more information,
|
||||
see: https://cloud.google.com/sdk/usage-statistics
|
||||
This value is set by your choices during installation, but can be
|
||||
changed at any time. For more information, see Usage statistics.
|
||||
|
||||
enable_feature_flags
|
||||
If True, remote config-file driven feature flags will be enabled.
|
||||
|
|
|
|||
|
|
@ -109,9 +109,8 @@ AVAILABLE PROPERTIES
|
|||
|
||||
disable_usage_reporting
|
||||
If True, anonymous statistics on SDK usage will not be collected.
|
||||
This value is set by default based on your choices during
|
||||
installation, but can be changed at any time. For more information,
|
||||
see: https://cloud.google.com/sdk/usage-statistics
|
||||
This value is set by your choices during installation, but can be
|
||||
changed at any time. For more information, see Usage statistics.
|
||||
|
||||
enable_feature_flags
|
||||
If True, remote config-file driven feature flags will be enabled.
|
||||
|
|
|
|||
|
|
@ -118,9 +118,8 @@ AVAILABLE PROPERTIES
|
|||
|
||||
disable_usage_reporting
|
||||
If True, anonymous statistics on SDK usage will not be collected.
|
||||
This value is set by default based on your choices during
|
||||
installation, but can be changed at any time. For more information,
|
||||
see: https://cloud.google.com/sdk/usage-statistics
|
||||
This value is set by your choices during installation, but can be
|
||||
changed at any time. For more information, see Usage statistics.
|
||||
|
||||
enable_feature_flags
|
||||
If True, remote config-file driven feature flags will be enabled.
|
||||
|
|
|
|||
|
|
@ -79,9 +79,8 @@ AVAILABLE PROPERTIES
|
|||
|
||||
disable_usage_reporting
|
||||
If True, anonymous statistics on SDK usage will not be collected.
|
||||
This value is set by default based on your choices during
|
||||
installation, but can be changed at any time. For more information,
|
||||
see: https://cloud.google.com/sdk/usage-statistics
|
||||
This value is set by your choices during installation, but can be
|
||||
changed at any time. For more information, see Usage statistics.
|
||||
|
||||
enable_feature_flags
|
||||
If True, remote config-file driven feature flags will be enabled.
|
||||
|
|
|
|||
|
|
@ -114,7 +114,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 container fleet memberships generate-gateway-rbac
|
||||
|
||||
$ gcloud beta container fleet memberships generate-gateway-rbac
|
||||
|
||||
|
|
|
|||
|
|
@ -118,11 +118,10 @@ EXAMPLES
|
|||
--service-account-key-file=/tmp/keyfile.json
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
Membership resource - The group of arguments defining a membership
|
||||
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:
|
||||
Membership resource - The group of arguments defining a membership. 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 MEMBERSHIP_NAME on the command line with a fully
|
||||
specified name;
|
||||
◆ provide the argument --project on the command line;
|
||||
|
|
@ -202,9 +201,8 @@ REQUIRED FLAGS
|
|||
Enable Workload Identity when registering the cluster with a fleet.
|
||||
Ensure that GKE Workload Identity is enabled on your GKE cluster,
|
||||
it is a requirement for using Workload Identity with memberships.
|
||||
Refer to the Registering a cluster using Workload Identity section
|
||||
in
|
||||
https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster#register_cluster
|
||||
Refer to the Enable GKE Workload Identity section in
|
||||
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable
|
||||
--service_account_key_file flag should not be set if this is set.
|
||||
|
||||
This flag must be specified if any of the other arguments in this
|
||||
|
|
|
|||
|
|
@ -59,11 +59,10 @@ EXAMPLES
|
|||
my-membership --gke-cluster=my-cluster-region-or-zone/my-cluster
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
Membership resource - The group of arguments defining a membership
|
||||
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:
|
||||
Membership resource - The group of arguments defining a membership. 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 MEMBERSHIP_NAME on the command line with a fully
|
||||
specified name;
|
||||
◆ provide the argument --project on the command line;
|
||||
|
|
|
|||
|
|
@ -114,7 +114,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 container hub memberships generate-gateway-rbac
|
||||
|
||||
$ gcloud beta container hub memberships generate-gateway-rbac
|
||||
|
||||
|
|
|
|||
|
|
@ -118,11 +118,10 @@ EXAMPLES
|
|||
--service-account-key-file=/tmp/keyfile.json
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
Membership resource - The group of arguments defining a membership
|
||||
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:
|
||||
Membership resource - The group of arguments defining a membership. 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 MEMBERSHIP_NAME on the command line with a fully
|
||||
specified name;
|
||||
◆ provide the argument --project on the command line;
|
||||
|
|
@ -202,9 +201,8 @@ REQUIRED FLAGS
|
|||
Enable Workload Identity when registering the cluster with a fleet.
|
||||
Ensure that GKE Workload Identity is enabled on your GKE cluster,
|
||||
it is a requirement for using Workload Identity with memberships.
|
||||
Refer to the Registering a cluster using Workload Identity section
|
||||
in
|
||||
https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster#register_cluster
|
||||
Refer to the Enable GKE Workload Identity section in
|
||||
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable
|
||||
--service_account_key_file flag should not be set if this is set.
|
||||
|
||||
This flag must be specified if any of the other arguments in this
|
||||
|
|
|
|||
|
|
@ -59,11 +59,10 @@ EXAMPLES
|
|||
--gke-cluster=my-cluster-region-or-zone/my-cluster
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
Membership resource - The group of arguments defining a membership
|
||||
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:
|
||||
Membership resource - The group of arguments defining a membership. 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 MEMBERSHIP_NAME on the command line with a fully
|
||||
specified name;
|
||||
◆ provide the argument --project on the command line;
|
||||
|
|
|
|||
|
|
@ -8,10 +8,11 @@ SYNOPSIS
|
|||
[--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION]
|
||||
[--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR]
|
||||
[--ignore-file=IGNORE_FILE] [--labels=[KEY=VALUE,...]]
|
||||
[--skaffold-file=SKAFFOLD_FILE] [--skaffold-version=SKAFFOLD_VERSION]
|
||||
[--source=SOURCE; default="."] [--to-target=TO_TARGET]
|
||||
[--skaffold-version=SKAFFOLD_VERSION] [--to-target=TO_TARGET]
|
||||
[--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]]
|
||||
[--disable-initial-rollout | --enable-initial-rollout]
|
||||
[--from-k8s-manifest=FROM_K8S_MANIFEST
|
||||
| --skaffold-file=SKAFFOLD_FILE --source=SOURCE; default="."]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -118,34 +119,9 @@ FLAGS
|
|||
$ gcloud alpha deploy releases create \
|
||||
--labels="commit=abc123,author=foo"
|
||||
|
||||
--skaffold-file=SKAFFOLD_FILE
|
||||
Path of the skaffold file relative to the source directory.
|
||||
|
||||
Examples:
|
||||
|
||||
Use Skaffold file:
|
||||
|
||||
$ gcloud alpha deploy releases create --source=/home/user/source \
|
||||
--skaffold-file=config/skaffold.yaml
|
||||
|
||||
The skaffold file absolute file path is expected to be:
|
||||
/home/user/source/config/skaffold.yaml
|
||||
|
||||
--skaffold-version=SKAFFOLD_VERSION
|
||||
Version of the Skaffold binary.
|
||||
|
||||
--source=SOURCE; default="."
|
||||
The location of the source that contains skaffold.yaml. The location
|
||||
can be a directory on a local disk or a gzipped archive file (.tar.gz)
|
||||
in Google Cloud Storage. If the source is a local directory, this
|
||||
command skips the files specified in the --ignore-file. If
|
||||
--ignore-file is not specified, use.gcloudignore file. If a
|
||||
.gcloudignore file is absent and a .gitignore file is present in the
|
||||
local source directory, gcloud will use a generated Git-compatible
|
||||
.gcloudignore file that respects your .gitignored files. The global
|
||||
.gitignore is not respected. For more information on .gcloudignore, see
|
||||
gcloud topic gcloudignore.
|
||||
|
||||
--to-target=TO_TARGET
|
||||
Specifies a target to deliver into upon release creation
|
||||
|
||||
|
|
@ -176,6 +152,40 @@ FLAGS
|
|||
Creates a rollout in the first target defined in the delivery
|
||||
pipeline. This is the default behavior.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--from-k8s-manifest=FROM_K8S_MANIFEST
|
||||
The path to a Kubernetes manifest, which Cloud Deploy will use to
|
||||
generate a skaffold.yaml file for you (for example, foo/bar/k8.yaml).
|
||||
The generated Skaffold file will be available in the Google Cloud
|
||||
Storage source staging directory (see --gcs-source-staging-dir flag)
|
||||
after the release is complete.
|
||||
|
||||
--skaffold-file=SKAFFOLD_FILE
|
||||
Path of the skaffold file relative to the source directory.
|
||||
|
||||
Examples:
|
||||
|
||||
Use Skaffold file:
|
||||
|
||||
$ gcloud alpha deploy releases create --source=/home/user/source \
|
||||
--skaffold-file=config/skaffold.yaml
|
||||
|
||||
The skaffold file absolute file path is expected to be:
|
||||
/home/user/source/config/skaffold.yaml
|
||||
|
||||
--source=SOURCE; default="."
|
||||
The location of the source that contains skaffold.yaml. The location
|
||||
can be a directory on a local disk or a gzipped archive file
|
||||
(.tar.gz) in Google Cloud Storage. If the source is a local
|
||||
directory, this command skips the files specified in the
|
||||
--ignore-file. If --ignore-file is not specified, use.gcloudignore
|
||||
file. If a .gcloudignore file is absent and a .gitignore file is
|
||||
present in the local source directory, gcloud will use a generated
|
||||
Git-compatible .gcloudignore file that respects your .gitignored
|
||||
files. The global .gitignore is not respected. For more information
|
||||
on .gcloudignore, see gcloud topic gcloudignore.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -15,8 +15,8 @@ EXAMPLES
|
|||
|
||||
To see the DS records for every key-signing DnsKey in a managed zone, run:
|
||||
|
||||
$ gcloud alpha dns dns-keys list --zone=my_zone 3 \
|
||||
--format='value(ds_record())' --filter='type=keySigning'
|
||||
$ gcloud alpha dns dns-keys list --zone=my_zone \
|
||||
--filter='type=keySigning' --format='value(ds_record())'
|
||||
|
||||
REQUIRED FLAGS
|
||||
--zone=ZONE, -z ZONE
|
||||
|
|
|
|||
|
|
@ -44,9 +44,16 @@ COMMANDS
|
|||
get-transfer-parameters
|
||||
(ALPHA) Get transfer parameters of a specific domain.
|
||||
|
||||
import
|
||||
(ALPHA) Import a domain from Google Domains registrar to Cloud Domains.
|
||||
|
||||
list
|
||||
(ALPHA) List Cloud Domains registrations.
|
||||
|
||||
list-importable-domains
|
||||
(ALPHA) List Google Domains registrations importable into Cloud
|
||||
Domains.
|
||||
|
||||
register
|
||||
(ALPHA) Register a new domain.
|
||||
|
||||
|
|
|
|||
76
gcloud/alpha/domains/registrations/import
Normal file
76
gcloud/alpha/domains/registrations/import
Normal file
|
|
@ -0,0 +1,76 @@
|
|||
NAME
|
||||
gcloud alpha domains registrations import - import a domain from Google
|
||||
Domains registrar to Cloud Domains
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha domains registrations import REGISTRATION [--async]
|
||||
[--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Create a new Cloud Domains registration resource by importing an
|
||||
existing domain from Google Domains registrar. The new resource's ID will
|
||||
be equal to the domain name.
|
||||
|
||||
After this command executes, a resource is created with state ACTIVE,
|
||||
indicating that the import was successful. Cloud Domains will automatically
|
||||
renew your domain as long as your Cloud Billing account is active. If this
|
||||
command fails, no resource is created.
|
||||
|
||||
Other users may lose access to the domain and will need IAM permissions on
|
||||
the Cloud project containing the registration resource to regain access.
|
||||
|
||||
EXAMPLES
|
||||
To import example.com, run:
|
||||
|
||||
$ gcloud alpha domains registrations import example.com
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
Registration resource - The domain name to import. 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 registration on the command line with a fully
|
||||
specified name;
|
||||
◆ provide the argument --project on the command line;
|
||||
◆ set the property core/project. To set the location attribute:
|
||||
◆ provide the argument registration on the command line with a fully
|
||||
specified name;
|
||||
◆ location is always global.
|
||||
|
||||
This must be specified.
|
||||
|
||||
REGISTRATION
|
||||
ID of the registration or fully qualified identifier for the
|
||||
registration. To set the registration attribute:
|
||||
▸ provide the argument registration on the command line.
|
||||
|
||||
FLAGS
|
||||
--async
|
||||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
||||
--labels=[KEY=VALUE,...]
|
||||
List of label KEY=VALUE pairs to add.
|
||||
|
||||
Keys must start with a lowercase character and contain only hyphens
|
||||
(-), underscores (_), lowercase characters, and numbers. Values must
|
||||
contain only hyphens (-), underscores (_), lowercase characters, and
|
||||
numbers.
|
||||
|
||||
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. These variants are also available:
|
||||
|
||||
$ gcloud domains registrations import
|
||||
|
||||
$ gcloud beta domains registrations import
|
||||
|
||||
71
gcloud/alpha/domains/registrations/list-importable-domains
Normal file
71
gcloud/alpha/domains/registrations/list-importable-domains
Normal file
|
|
@ -0,0 +1,71 @@
|
|||
NAME
|
||||
gcloud alpha domains registrations list-importable-domains - list Google
|
||||
Domains registrations importable into Cloud Domains
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha domains registrations list-importable-domains
|
||||
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
|
||||
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) List Google Domains registrations that can be imported to a Cloud
|
||||
Domains project.
|
||||
|
||||
Registrations with an IMPORTABLE resource state can be imported from Google
|
||||
Domains registrar to Cloud Domains.
|
||||
|
||||
Registrations with a SUSPENDED, EXPIRED, or DELETED resource state must
|
||||
have their states resolved with Google Domains registrar to be imported.
|
||||
|
||||
Registrations with an UNSUPPORTED resource state are not currently
|
||||
supported for import.
|
||||
|
||||
EXAMPLES
|
||||
To list Google Domains registrations that can be imported, run:
|
||||
|
||||
$ gcloud alpha domains registrations list-importable-domains
|
||||
|
||||
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.
|
||||
|
||||
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. These variants are also available:
|
||||
|
||||
$ gcloud domains registrations list-importable-domains
|
||||
|
||||
$ gcloud beta domains registrations list-importable-domains
|
||||
|
||||
|
|
@ -72,7 +72,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 functions add-invoker-policy-binding
|
||||
|
||||
$ gcloud beta functions add-invoker-policy-binding
|
||||
|
||||
|
|
|
|||
|
|
@ -2,21 +2,14 @@ NAME
|
|||
gcloud alpha functions list - list Google Cloud Functions
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha functions list [--gen2]
|
||||
[--regions=REGION,[REGION,...]; default="-"] [--filter=EXPRESSION]
|
||||
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
gcloud alpha functions list [--regions=REGION,[REGION,...]; default="-"]
|
||||
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
|
||||
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) List Google Cloud Functions.
|
||||
|
||||
FLAGS
|
||||
--gen2
|
||||
If enabled, this command will use Cloud Functions (Second generation).
|
||||
If disabled, Cloud Functions (First generation) will be used. If not
|
||||
specified, the value of this flag will be taken from the functions/gen2
|
||||
configuration property.
|
||||
|
||||
--regions=REGION,[REGION,...]; default="-"
|
||||
Regions containing functions to list. By default, functions from the
|
||||
region configured in [functions/region] property are listed.
|
||||
|
|
|
|||
|
|
@ -76,7 +76,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 functions remove-invoker-policy-binding
|
||||
|
||||
$ gcloud beta functions remove-invoker-policy-binding
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha iap tcp dest-groups add-iam-policy-binding
|
||||
--group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE
|
||||
--dest-group=DEST_GROUP --member=PRINCIPAL --region=REGION --role=ROLE
|
||||
[--condition=[KEY=VALUE,...]
|
||||
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -21,7 +21,7 @@ EXAMPLES
|
|||
$ gcloud alpha iap tcp dest-groups add-iam-policy-binding \
|
||||
--member='user:test-user@gmail.com' \
|
||||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To add an IAM policy binding for the role of
|
||||
'roles/iap.tunnelResourceAccessor' for all authenticated users in the group
|
||||
|
|
@ -30,7 +30,7 @@ EXAMPLES
|
|||
$ gcloud alpha iap tcp dest-groups add-iam-policy-binding \
|
||||
--member='allAuthenticatedUsers' \
|
||||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To add an IAM policy binding which expires at the end of the year 2018 for
|
||||
the role of 'roles/iap.tunnelResourceAccessor' and the user
|
||||
|
|
@ -42,13 +42,13 @@ EXAMPLES
|
|||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--condition='expression=request.time <
|
||||
timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,
|
||||
description=Expires at midnight on 2018-12-31' --group-name='my-group' --region='us-west1'
|
||||
description=Expires at midnight on 2018-12-31' --dest-group='my-group' --region='us-west1'
|
||||
|
||||
See https://cloud.google.com/iam/docs/managing-policies for details of
|
||||
policy role and member types.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--group-name=GROUP_NAME
|
||||
--dest-group=DEST_GROUP
|
||||
Name of the Destination Group.
|
||||
|
||||
--member=PRINCIPAL
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ NAME
|
|||
TCP Destination Group resource
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha iap tcp dest-groups get-iam-policy --group-name=GROUP_NAME
|
||||
gcloud alpha iap tcp dest-groups get-iam-policy --dest-group=DEST_GROUP
|
||||
--region=REGION [--filter=EXPRESSION] [--limit=LIMIT]
|
||||
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -21,17 +21,17 @@ EXAMPLES
|
|||
run:
|
||||
|
||||
$ gcloud alpha iap tcp dest-groups get-iam-policy \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To get the IAM policy for the TCP Destination Group resource with name
|
||||
'my-group' and located in the region 'us-west1' within project 'project',
|
||||
run:
|
||||
|
||||
$ gcloud alpha iap tcp dest-groups get-iam-policy \
|
||||
--group-name='my-group' --region='us-west1' --project='project'
|
||||
--dest-group='my-group' --region='us-west1' --project='project'
|
||||
|
||||
REQUIRED FLAGS
|
||||
--group-name=GROUP_NAME
|
||||
--dest-group=DEST_GROUP
|
||||
Name of the Destination Group.
|
||||
|
||||
--region=REGION
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha iap tcp dest-groups remove-iam-policy-binding
|
||||
--group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE
|
||||
--dest-group=DEST_GROUP --member=PRINCIPAL --region=REGION --role=ROLE
|
||||
[--all | --condition=[KEY=VALUE,...]
|
||||
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -21,7 +21,7 @@ EXAMPLES
|
|||
$ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \
|
||||
--member='user:test-user@gmail.com' \
|
||||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To remove an IAM policy binding for the role of
|
||||
'roles/iap.tunnelResourceAccessor' from all authenticated users in the
|
||||
|
|
@ -30,7 +30,7 @@ EXAMPLES
|
|||
$ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \
|
||||
--member='allAuthenticatedUsers' \
|
||||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To remove an IAM policy binding which expires at the end of the year 2018
|
||||
for the role of 'roles/iap.tunnelResourceAccessor' for the user
|
||||
|
|
@ -43,7 +43,7 @@ EXAMPLES
|
|||
--condition='expression=request.time <
|
||||
timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,
|
||||
description=Expires at midnight on 2018-12-31' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
To remove all IAM policy bindings regardless of the condition for the role
|
||||
of 'roles/iap.tunnelResourceAccessor' and for the user
|
||||
|
|
@ -53,13 +53,13 @@ EXAMPLES
|
|||
$ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \
|
||||
--member='user:test-user@gmail.com' \
|
||||
--role='roles/iap.tunnelResourceAccessor' \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group='my-group' --region='us-west1'
|
||||
|
||||
See https://cloud.google.com/iam/docs/managing-policies for details of
|
||||
policy role and member types.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--group-name=GROUP_NAME
|
||||
--dest-group=DEST_GROUP
|
||||
Name of the Destination Group.
|
||||
|
||||
--member=PRINCIPAL
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE
|
||||
--group-name=GROUP_NAME --region=REGION [GCLOUD_WIDE_FLAG ...]
|
||||
--dest-group=DEST_GROUP --region=REGION [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) This command replaces the existing IAM policy for an IAP TCP
|
||||
|
|
@ -22,20 +22,21 @@ EXAMPLES
|
|||
run:
|
||||
|
||||
$ gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE \
|
||||
--group-name='my-group' --region='us-west1'
|
||||
--dest-group=='my-group' --region='us-west1'
|
||||
|
||||
To set the IAM policy for the TCP Destination Group resource within project
|
||||
PROJECT_ID in the group 'my-group' located in the region 'us-west1', run:
|
||||
|
||||
$ gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE \
|
||||
--project=PROJECT_ID --group-name='my-group' --region='us-west1'
|
||||
--project=PROJECT_ID --dest-group=='my-group' \
|
||||
--region='us-west1'
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
POLICY_FILE
|
||||
JSON or YAML file containing the IAM policy.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--group-name=GROUP_NAME
|
||||
--dest-group=DEST_GROUP
|
||||
Name of the Destination Group.
|
||||
|
||||
--region=REGION
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha logging sinks create SINK_NAME DESTINATION
|
||||
[--custom-writer-identity=SERVICE_ACCOUNT_EMAIL]
|
||||
[--description=DESCRIPTION] [--disabled]
|
||||
[--exclusion=[description=DESCRIPTION],
|
||||
[disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children]
|
||||
|
|
@ -69,6 +70,11 @@ POSITIONAL ARGUMENTS
|
|||
The destination for the sink.
|
||||
|
||||
FLAGS
|
||||
--custom-writer-identity=SERVICE_ACCOUNT_EMAIL
|
||||
Writer identity for the sink. Only available for writing to
|
||||
cross-project LogBucket sinks. Note a writer identity is automatically
|
||||
generated if needed for the sink when it is not explicitly provided.
|
||||
|
||||
--description=DESCRIPTION
|
||||
Description of the sink.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ SYNOPSIS
|
|||
gcloud alpha logging sinks update SINK_NAME [DESTINATION]
|
||||
[--add-exclusion=[description=DESCRIPTION],
|
||||
[disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions]
|
||||
[--custom-writer-identity=SERVICE_ACCOUNT_EMAIL]
|
||||
[--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER]
|
||||
[--remove-exclusions=[EXCLUSION ID,...]]
|
||||
[--update-exclusion=[description=DESCRIPTION],
|
||||
|
|
@ -65,6 +66,11 @@ FLAGS
|
|||
--clear-exclusions
|
||||
Remove all logging exclusions from the sink.
|
||||
|
||||
--custom-writer-identity=SERVICE_ACCOUNT_EMAIL
|
||||
Writer identity for the sink. Only available for writing to
|
||||
cross-project LogBucket sinks. Note a writer identity is automatically
|
||||
generated if needed for the sink when it is not explicitly provided.
|
||||
|
||||
--description=DESCRIPTION
|
||||
Description of the sink.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@ NAME
|
|||
gcloud alpha run integrations create - create a Cloud Run Integration
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha run integrations create --service=SERVICE --type=TYPE
|
||||
[--name=NAME] [--parameters=[PARAMETER=VALUE,...]] [--region=REGION]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
gcloud alpha run integrations create --type=TYPE [--name=NAME]
|
||||
[--parameters=[PARAMETER=VALUE,...]] [--region=REGION]
|
||||
[--service=SERVICE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Create a Cloud Run Integration.
|
||||
|
|
@ -21,9 +21,6 @@ EXAMPLES
|
|||
--service=myservice --parameters=domain=mydomain.com
|
||||
|
||||
REQUIRED FLAGS
|
||||
--service=SERVICE
|
||||
Name of the Cloud Run service to attach to the integration.
|
||||
|
||||
--type=TYPE
|
||||
Type of the integration. To see available types and usage, use "gcloud
|
||||
run integrations types list" command.
|
||||
|
|
@ -41,6 +38,10 @@ OPTIONAL FLAGS
|
|||
Region in which the resource can be found. Alternatively, set the
|
||||
property [run/region].
|
||||
|
||||
--service=SERVICE
|
||||
Name of the Cloud Run service to attach to the integration. It is
|
||||
required for some integrations.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -8,8 +8,8 @@ SYNOPSIS
|
|||
[--content-encoding=CONTENT_ENCODING]
|
||||
[--content-language=CONTENT_LANGUAGE] [--content-md5=MD5_DIGEST]
|
||||
[--content-type=CONTENT_TYPE] [--continue-on-error, -c]
|
||||
[--custom-metadata=[CUSTOM_METADATA,...]] [--custom-time=CUSTOM_TIME]
|
||||
[--do-not-decompress] [--if-generation-match=GENERATION]
|
||||
[--custom-time=CUSTOM_TIME] [--do-not-decompress]
|
||||
[--if-generation-match=GENERATION]
|
||||
[--if-metageneration-match=METAGENERATION] [--ignore-symlinks]
|
||||
[--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH]
|
||||
[--preserve-posix, -P] [--print-created-message, -v]
|
||||
|
|
@ -19,6 +19,10 @@ SYNOPSIS
|
|||
[--canned-acl=PREDEFINED_ACL,
|
||||
--predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL
|
||||
| --preserve-acl, -p]
|
||||
[--clear-custom-metadata
|
||||
| --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]
|
||||
| --remove-custom-metadata=[METADATA_KEYS,...]
|
||||
--update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]]
|
||||
[--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...]
|
||||
| --gzip-in-flight-all, -J
|
||||
| --gzip-local=[FILE_EXTENSIONS,...], -z [FILE_EXTENSIONS,...]
|
||||
|
|
@ -97,9 +101,6 @@ FLAGS
|
|||
flag takes effect only in sequential execution mode (i.e. processor and
|
||||
thread count are set to 1). Parallelism is default.
|
||||
|
||||
--custom-metadata=[CUSTOM_METADATA,...]
|
||||
Custom metadata fields set by user.
|
||||
|
||||
--custom-time=CUSTOM_TIME
|
||||
Custom time for Google Cloud Storage objects in RFC 3339 format.
|
||||
|
||||
|
|
@ -192,6 +193,34 @@ FLAGS
|
|||
also set a default object ACL on that bucket instead of using this
|
||||
flag.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-custom-metadata
|
||||
Clears all custom metadata on objects. When used with
|
||||
--preserve-posix, POSIX attributes will still be stored in custom
|
||||
metadata.
|
||||
|
||||
--custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]
|
||||
Sets custom metadata on objects. When used with --preserve-posix,
|
||||
POSIX attributes are also stored in custom metadata.
|
||||
|
||||
Flags that preserve unspecified existing metadata cannot be used with
|
||||
--custom-metadata or --clear-custom-metadata, but can be specified
|
||||
together:
|
||||
|
||||
--remove-custom-metadata=[METADATA_KEYS,...]
|
||||
Removes individual custom metadata keys from objects. This flag can
|
||||
be used with --update-custom-metadata. When used with
|
||||
--preserve-posix, POSIX attributes specified by this flag are not
|
||||
preserved.
|
||||
|
||||
--update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]
|
||||
Adds or sets individual custom metadata key value pairs on objects.
|
||||
Existing custom metadata not specified with this flag is not
|
||||
changed. This flag can be used with --remove-custom-metadata. When
|
||||
keys overlap with those provided by --preserve-posix, values
|
||||
specified by this flag are used.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue