From 3513fd1c113afef267ce49740c02da25412ac0d5 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 27 Jul 2022 08:55:33 +0000 Subject: [PATCH] gcloud: Wed Jul 27 08:55:33 UTC 2022 --- gcloud/_version | 8 +- gcloud/ai/models/upload | 7 +- gcloud/alpha/ai/models/upload | 7 +- gcloud/alpha/anthos/config/controller/list | 14 +- .../alpha/beyondcorp/app/connections/create | 4 +- .../alpha/beyondcorp/app/connections/delete | 4 +- .../alpha/beyondcorp/app/connections/describe | 4 +- gcloud/alpha/beyondcorp/app/connections/help | 4 +- gcloud/alpha/beyondcorp/app/connections/list | 4 +- .../alpha/beyondcorp/app/connections/update | 4 +- gcloud/alpha/beyondcorp/app/connectors/create | 4 +- gcloud/alpha/beyondcorp/app/connectors/delete | 4 +- .../alpha/beyondcorp/app/connectors/describe | 4 +- gcloud/alpha/beyondcorp/app/connectors/help | 4 +- gcloud/alpha/beyondcorp/app/connectors/list | 4 +- gcloud/alpha/beyondcorp/app/connectors/update | 4 +- gcloud/alpha/beyondcorp/app/help | 4 +- .../alpha/beyondcorp/app/operations/describe | 4 +- gcloud/alpha/beyondcorp/app/operations/help | 4 +- gcloud/alpha/beyondcorp/app/operations/list | 4 +- .../client-connector/gateways/create | 4 +- .../client-connector/gateways/delete | 4 +- .../client-connector/gateways/describe | 4 +- .../beyondcorp/client-connector/gateways/help | 4 +- .../beyondcorp/client-connector/gateways/list | 4 +- gcloud/alpha/beyondcorp/client-connector/help | 4 +- .../client-connector/operations/describe | 4 +- .../client-connector/operations/help | 4 +- .../client-connector/operations/list | 4 +- .../client-connector/services/create | 4 +- .../client-connector/services/delete | 4 +- .../client-connector/services/describe | 4 +- .../beyondcorp/client-connector/services/help | 4 +- .../beyondcorp/client-connector/services/list | 4 +- .../client-connector/services/update | 4 +- gcloud/alpha/beyondcorp/help | 4 +- gcloud/alpha/compute/disks/create | 4 +- .../compute/firewall-policies/rules/create | 2 +- .../compute/firewall-policies/rules/update | 2 +- gcloud/alpha/compute/images/create | 4 +- gcloud/alpha/compute/images/update | 14 +- .../alpha/compute/instance-templates/create | 15 +- .../network-firewall-policies/rules/create | 2 +- .../network-firewall-policies/rules/update | 2 +- gcloud/alpha/compute/os-config/troubleshoot | 2 + .../compute/security-policies/rules/create | 12 ++ .../compute/security-policies/rules/update | 12 ++ gcloud/alpha/config/help | 5 +- gcloud/alpha/config/list | 5 +- gcloud/alpha/config/set | 5 +- gcloud/alpha/config/unset | 5 +- .../fleet/memberships/generate-gateway-rbac | 4 +- .../container/fleet/memberships/register | 14 +- .../container/fleet/memberships/unregister | 9 +- .../hub/memberships/generate-gateway-rbac | 4 +- .../alpha/container/hub/memberships/register | 14 +- .../container/hub/memberships/unregister | 9 +- gcloud/alpha/deploy/releases/create | 64 ++++---- gcloud/alpha/dns/dns-keys/list | 4 +- gcloud/alpha/domains/registrations/help | 7 + gcloud/alpha/domains/registrations/import | 76 ++++++++++ .../registrations/list-importable-domains | 71 +++++++++ .../functions/add-invoker-policy-binding | 4 +- gcloud/alpha/functions/list | 13 +- .../functions/remove-invoker-policy-binding | 4 +- .../tcp/dest-groups/add-iam-policy-binding | 10 +- .../alpha/iap/tcp/dest-groups/get-iam-policy | 8 +- .../tcp/dest-groups/remove-iam-policy-binding | 12 +- .../alpha/iap/tcp/dest-groups/set-iam-policy | 9 +- gcloud/alpha/logging/sinks/create | 6 + gcloud/alpha/logging/sinks/update | 6 + gcloud/alpha/run/integrations/create | 13 +- gcloud/alpha/storage/cp | 39 ++++- gcloud/anthos/config/controller/list | 10 +- gcloud/artifacts/packages/describe | 75 ++++++++++ gcloud/artifacts/packages/help | 3 + gcloud/beta/ai/models/upload | 7 +- gcloud/beta/beyondcorp/app/connections/create | 129 ++++++++++++++++ gcloud/beta/beyondcorp/app/connections/delete | 67 +++++++++ .../beta/beyondcorp/app/connections/describe | 72 +++++++++ gcloud/beta/beyondcorp/app/connections/help | 42 ++++++ gcloud/beta/beyondcorp/app/connections/list | 88 +++++++++++ gcloud/beta/beyondcorp/app/connections/update | 117 +++++++++++++++ gcloud/beta/beyondcorp/app/connectors/create | 98 ++++++++++++ gcloud/beta/beyondcorp/app/connectors/delete | 67 +++++++++ .../beta/beyondcorp/app/connectors/describe | 75 ++++++++++ gcloud/beta/beyondcorp/app/connectors/help | 43 ++++++ gcloud/beta/beyondcorp/app/connectors/list | 87 +++++++++++ gcloud/beta/beyondcorp/app/connectors/update | 106 +++++++++++++ gcloud/beta/beyondcorp/app/help | 43 ++++++ .../beta/beyondcorp/app/operations/describe | 67 +++++++++ gcloud/beta/beyondcorp/app/operations/help | 30 ++++ gcloud/beta/beyondcorp/app/operations/list | 82 +++++++++++ .../client-connector/gateways/create | 88 +++++++++++ .../client-connector/gateways/delete | 69 +++++++++ .../client-connector/gateways/describe | 65 ++++++++ .../beyondcorp/client-connector/gateways/help | 42 ++++++ .../beyondcorp/client-connector/gateways/list | 81 ++++++++++ gcloud/beta/beyondcorp/client-connector/help | 44 ++++++ .../client-connector/operations/describe | 67 +++++++++ .../client-connector/operations/help | 31 ++++ .../client-connector/operations/list | 82 +++++++++++ .../client-connector/services/create | 139 ++++++++++++++++++ .../client-connector/services/delete | 73 +++++++++ .../client-connector/services/describe | 67 +++++++++ .../beyondcorp/client-connector/services/help | 47 ++++++ .../beyondcorp/client-connector/services/list | 87 +++++++++++ .../client-connector/services/update | 81 ++++++++++ gcloud/beta/beyondcorp/help | 41 ++++++ gcloud/beta/compute/images/update | 14 +- .../compute/security-policies/rules/create | 4 + .../compute/security-policies/rules/update | 4 + gcloud/beta/config/get | 5 +- gcloud/beta/config/help | 5 +- gcloud/beta/config/list | 5 +- gcloud/beta/config/set | 5 +- gcloud/beta/config/unset | 5 +- .../fleet/memberships/generate-gateway-rbac | 6 +- .../beta/container/fleet/memberships/register | 5 +- .../hub/memberships/generate-gateway-rbac | 6 +- .../beta/container/hub/memberships/register | 5 +- gcloud/beta/datastream/streams/create | 43 ++---- gcloud/beta/datastream/streams/update | 42 ++---- gcloud/beta/deploy/releases/create | 64 ++++---- gcloud/beta/dns/dns-keys/list | 4 +- gcloud/beta/domains/registrations/help | 6 + gcloud/beta/domains/registrations/import | 74 ++++++++++ .../registrations/list-importable-domains | 69 +++++++++ .../beta/functions/add-invoker-policy-binding | 6 +- gcloud/beta/functions/list | 13 +- .../functions/remove-invoker-policy-binding | 6 +- .../tcp/dest-groups/add-iam-policy-binding | 10 +- .../beta/iap/tcp/dest-groups/get-iam-policy | 8 +- .../tcp/dest-groups/remove-iam-policy-binding | 12 +- .../beta/iap/tcp/dest-groups/set-iam-policy | 9 +- gcloud/compute/security-policies/rules/create | 4 + gcloud/compute/security-policies/rules/update | 4 + gcloud/config/get | 5 +- gcloud/config/help | 5 +- gcloud/config/list | 5 +- gcloud/config/set | 5 +- gcloud/config/unset | 5 +- .../fleet/memberships/generate-gateway-rbac | 118 +++++++++++++++ gcloud/container/fleet/memberships/help | 3 + gcloud/container/fleet/memberships/register | 5 +- .../hub/memberships/generate-gateway-rbac | 118 +++++++++++++++ gcloud/container/hub/memberships/help | 3 + gcloud/container/hub/memberships/register | 5 +- gcloud/datastream/streams/create | 43 ++---- gcloud/datastream/streams/update | 42 ++---- gcloud/deploy/releases/create | 64 ++++---- gcloud/dns/dns-keys/list | 4 +- gcloud/domains/registrations/help | 6 + gcloud/domains/registrations/import | 73 +++++++++ .../registrations/list-importable-domains | 68 +++++++++ gcloud/functions/add-iam-policy-binding | 9 +- gcloud/functions/add-invoker-policy-binding | 77 ++++++++++ gcloud/functions/call | 26 +++- gcloud/functions/delete | 10 +- gcloud/functions/deploy | 62 +++++++- gcloud/functions/describe | 10 +- gcloud/functions/event-types/list | 9 +- gcloud/functions/get-iam-policy | 9 +- gcloud/functions/help | 7 + gcloud/functions/logs/read | 8 +- gcloud/functions/regions/list | 11 +- gcloud/functions/remove-iam-policy-binding | 9 +- .../functions/remove-invoker-policy-binding | 81 ++++++++++ gcloud/functions/set-iam-policy | 9 +- gcloud/healthcare/fhir-stores/export/bq | 8 +- gcloud/run/deploy | 5 +- 171 files changed, 3989 insertions(+), 448 deletions(-) create mode 100644 gcloud/alpha/domains/registrations/import create mode 100644 gcloud/alpha/domains/registrations/list-importable-domains create mode 100644 gcloud/artifacts/packages/describe create mode 100644 gcloud/beta/beyondcorp/app/connections/create create mode 100644 gcloud/beta/beyondcorp/app/connections/delete create mode 100644 gcloud/beta/beyondcorp/app/connections/describe create mode 100644 gcloud/beta/beyondcorp/app/connections/help create mode 100644 gcloud/beta/beyondcorp/app/connections/list create mode 100644 gcloud/beta/beyondcorp/app/connections/update create mode 100644 gcloud/beta/beyondcorp/app/connectors/create create mode 100644 gcloud/beta/beyondcorp/app/connectors/delete create mode 100644 gcloud/beta/beyondcorp/app/connectors/describe create mode 100644 gcloud/beta/beyondcorp/app/connectors/help create mode 100644 gcloud/beta/beyondcorp/app/connectors/list create mode 100644 gcloud/beta/beyondcorp/app/connectors/update create mode 100644 gcloud/beta/beyondcorp/app/help create mode 100644 gcloud/beta/beyondcorp/app/operations/describe create mode 100644 gcloud/beta/beyondcorp/app/operations/help create mode 100644 gcloud/beta/beyondcorp/app/operations/list create mode 100644 gcloud/beta/beyondcorp/client-connector/gateways/create create mode 100644 gcloud/beta/beyondcorp/client-connector/gateways/delete create mode 100644 gcloud/beta/beyondcorp/client-connector/gateways/describe create mode 100644 gcloud/beta/beyondcorp/client-connector/gateways/help create mode 100644 gcloud/beta/beyondcorp/client-connector/gateways/list create mode 100644 gcloud/beta/beyondcorp/client-connector/help create mode 100644 gcloud/beta/beyondcorp/client-connector/operations/describe create mode 100644 gcloud/beta/beyondcorp/client-connector/operations/help create mode 100644 gcloud/beta/beyondcorp/client-connector/operations/list create mode 100644 gcloud/beta/beyondcorp/client-connector/services/create create mode 100644 gcloud/beta/beyondcorp/client-connector/services/delete create mode 100644 gcloud/beta/beyondcorp/client-connector/services/describe create mode 100644 gcloud/beta/beyondcorp/client-connector/services/help create mode 100644 gcloud/beta/beyondcorp/client-connector/services/list create mode 100644 gcloud/beta/beyondcorp/client-connector/services/update create mode 100644 gcloud/beta/beyondcorp/help create mode 100644 gcloud/beta/domains/registrations/import create mode 100644 gcloud/beta/domains/registrations/list-importable-domains create mode 100644 gcloud/container/fleet/memberships/generate-gateway-rbac create mode 100644 gcloud/container/hub/memberships/generate-gateway-rbac create mode 100644 gcloud/domains/registrations/import create mode 100644 gcloud/domains/registrations/list-importable-domains create mode 100644 gcloud/functions/add-invoker-policy-binding create mode 100644 gcloud/functions/remove-invoker-policy-binding diff --git a/gcloud/_version b/gcloud/_version index bc278cef2..36062d72a 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 394.0.0 -alpha 2022.07.19 -beta 2022.07.19 +Google Cloud SDK 395.0.0 +alpha 2022.07.22 +beta 2022.07.22 bq 2.0.75 -core 2022.07.19 +core 2022.07.22 gsutil 5.11 diff --git a/gcloud/ai/models/upload b/gcloud/ai/models/upload index c057e389c..806e53dbb 100644 --- a/gcloud/ai/models/upload +++ b/gcloud/ai/models/upload @@ -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, diff --git a/gcloud/alpha/ai/models/upload b/gcloud/alpha/ai/models/upload index e8faf4859..3ac814cc9 100644 --- a/gcloud/alpha/ai/models/upload +++ b/gcloud/alpha/ai/models/upload @@ -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, diff --git a/gcloud/alpha/anthos/config/controller/list b/gcloud/alpha/anthos/config/controller/list index b8148a459..96d9ccf58 100644 --- a/gcloud/alpha/anthos/config/controller/list +++ b/gcloud/alpha/anthos/config/controller/list @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connections/create b/gcloud/alpha/beyondcorp/app/connections/create index f1a9c5b93..6aba52c8e 100644 --- a/gcloud/alpha/beyondcorp/app/connections/create +++ b/gcloud/alpha/beyondcorp/app/connections/create @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connections/delete b/gcloud/alpha/beyondcorp/app/connections/delete index 3bff330a5..3abffbdbd 100644 --- a/gcloud/alpha/beyondcorp/app/connections/delete +++ b/gcloud/alpha/beyondcorp/app/connections/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 app connections delete diff --git a/gcloud/alpha/beyondcorp/app/connections/describe b/gcloud/alpha/beyondcorp/app/connections/describe index 9a889c9c0..e665af454 100644 --- a/gcloud/alpha/beyondcorp/app/connections/describe +++ b/gcloud/alpha/beyondcorp/app/connections/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connections/help b/gcloud/alpha/beyondcorp/app/connections/help index b41723bcb..dbd098821 100644 --- a/gcloud/alpha/beyondcorp/app/connections/help +++ b/gcloud/alpha/beyondcorp/app/connections/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connections/list b/gcloud/alpha/beyondcorp/app/connections/list index 61d8dda94..5d72d1005 100644 --- a/gcloud/alpha/beyondcorp/app/connections/list +++ b/gcloud/alpha/beyondcorp/app/connections/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 app connections list diff --git a/gcloud/alpha/beyondcorp/app/connections/update b/gcloud/alpha/beyondcorp/app/connections/update index 2e71aa78e..71841e071 100644 --- a/gcloud/alpha/beyondcorp/app/connections/update +++ b/gcloud/alpha/beyondcorp/app/connections/update @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connectors/create b/gcloud/alpha/beyondcorp/app/connectors/create index 551dd000f..591b31e5e 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/create +++ b/gcloud/alpha/beyondcorp/app/connectors/create @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connectors/delete b/gcloud/alpha/beyondcorp/app/connectors/delete index c9d6884b5..790619054 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/delete +++ b/gcloud/alpha/beyondcorp/app/connectors/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 app connectors delete diff --git a/gcloud/alpha/beyondcorp/app/connectors/describe b/gcloud/alpha/beyondcorp/app/connectors/describe index 80fbb6f38..3294dfae6 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/describe +++ b/gcloud/alpha/beyondcorp/app/connectors/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connectors/help b/gcloud/alpha/beyondcorp/app/connectors/help index bbe94b224..c6a66da04 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/help +++ b/gcloud/alpha/beyondcorp/app/connectors/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connectors/list b/gcloud/alpha/beyondcorp/app/connectors/list index bbb909198..3ed593f05 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/list +++ b/gcloud/alpha/beyondcorp/app/connectors/list @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/connectors/update b/gcloud/alpha/beyondcorp/app/connectors/update index 05aea6ccf..45b9ccb4b 100644 --- a/gcloud/alpha/beyondcorp/app/connectors/update +++ b/gcloud/alpha/beyondcorp/app/connectors/update @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/help b/gcloud/alpha/beyondcorp/app/help index 75cb6b542..a9650c71b 100644 --- a/gcloud/alpha/beyondcorp/app/help +++ b/gcloud/alpha/beyondcorp/app/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/operations/describe b/gcloud/alpha/beyondcorp/app/operations/describe index 769a4ec6b..e08690bba 100644 --- a/gcloud/alpha/beyondcorp/app/operations/describe +++ b/gcloud/alpha/beyondcorp/app/operations/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/operations/help b/gcloud/alpha/beyondcorp/app/operations/help index f2f8a18ea..d93d06251 100644 --- a/gcloud/alpha/beyondcorp/app/operations/help +++ b/gcloud/alpha/beyondcorp/app/operations/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/app/operations/list b/gcloud/alpha/beyondcorp/app/operations/list index 7219899bf..3d04c29c9 100644 --- a/gcloud/alpha/beyondcorp/app/operations/list +++ b/gcloud/alpha/beyondcorp/app/operations/list @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/create b/gcloud/alpha/beyondcorp/client-connector/gateways/create index 53a9e0f87..76e0ac60c 100644 --- a/gcloud/alpha/beyondcorp/client-connector/gateways/create +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/create @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/delete b/gcloud/alpha/beyondcorp/client-connector/gateways/delete index f86ce9e7d..19fb97421 100644 --- a/gcloud/alpha/beyondcorp/client-connector/gateways/delete +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/delete @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/describe b/gcloud/alpha/beyondcorp/client-connector/gateways/describe index 78c6bd021..3c123e741 100644 --- a/gcloud/alpha/beyondcorp/client-connector/gateways/describe +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/help b/gcloud/alpha/beyondcorp/client-connector/gateways/help index b87b3aac9..67a6764d1 100644 --- a/gcloud/alpha/beyondcorp/client-connector/gateways/help +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/list b/gcloud/alpha/beyondcorp/client-connector/gateways/list index fa23ecee5..dd3698e6b 100644 --- a/gcloud/alpha/beyondcorp/client-connector/gateways/list +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/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 gateways list diff --git a/gcloud/alpha/beyondcorp/client-connector/help b/gcloud/alpha/beyondcorp/client-connector/help index e7f11198a..8d5e80615 100644 --- a/gcloud/alpha/beyondcorp/client-connector/help +++ b/gcloud/alpha/beyondcorp/client-connector/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/operations/describe b/gcloud/alpha/beyondcorp/client-connector/operations/describe index 6ada6952c..05a3989d9 100644 --- a/gcloud/alpha/beyondcorp/client-connector/operations/describe +++ b/gcloud/alpha/beyondcorp/client-connector/operations/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/operations/help b/gcloud/alpha/beyondcorp/client-connector/operations/help index 782f1fc2e..f21cf13be 100644 --- a/gcloud/alpha/beyondcorp/client-connector/operations/help +++ b/gcloud/alpha/beyondcorp/client-connector/operations/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/operations/list b/gcloud/alpha/beyondcorp/client-connector/operations/list index 2a6c32160..1989a0593 100644 --- a/gcloud/alpha/beyondcorp/client-connector/operations/list +++ b/gcloud/alpha/beyondcorp/client-connector/operations/list @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/create b/gcloud/alpha/beyondcorp/client-connector/services/create index add75ad5e..bc56bf492 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/create +++ b/gcloud/alpha/beyondcorp/client-connector/services/create @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/delete b/gcloud/alpha/beyondcorp/client-connector/services/delete index b25e9264d..8d5eef6eb 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/delete +++ b/gcloud/alpha/beyondcorp/client-connector/services/delete @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/describe b/gcloud/alpha/beyondcorp/client-connector/services/describe index 8329f0d57..c1b5c1929 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/describe +++ b/gcloud/alpha/beyondcorp/client-connector/services/describe @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/help b/gcloud/alpha/beyondcorp/client-connector/services/help index 000440549..a9fbd0b54 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/help +++ b/gcloud/alpha/beyondcorp/client-connector/services/help @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/list b/gcloud/alpha/beyondcorp/client-connector/services/list index c40496e42..6fd4cbd61 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/list +++ b/gcloud/alpha/beyondcorp/client-connector/services/list @@ -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 diff --git a/gcloud/alpha/beyondcorp/client-connector/services/update b/gcloud/alpha/beyondcorp/client-connector/services/update index ea40785d0..1cf276f35 100644 --- a/gcloud/alpha/beyondcorp/client-connector/services/update +++ b/gcloud/alpha/beyondcorp/client-connector/services/update @@ -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 diff --git a/gcloud/alpha/beyondcorp/help b/gcloud/alpha/beyondcorp/help index 000b275e9..e5d84d511 100644 --- a/gcloud/alpha/beyondcorp/help +++ b/gcloud/alpha/beyondcorp/help @@ -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 diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 3659a7240..cec03c4d1 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -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 diff --git a/gcloud/alpha/compute/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index 24f70a7e7..3b8e8796c 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -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 diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index d621e97b8..1e98f8f5d 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -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. diff --git a/gcloud/alpha/compute/images/create b/gcloud/alpha/compute/images/create index d608b8ba4..5da913f4a 100644 --- a/gcloud/alpha/compute/images/create +++ b/gcloud/alpha/compute/images/create @@ -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 diff --git a/gcloud/alpha/compute/images/update b/gcloud/alpha/compute/images/update index 973af13fa..6cee2a473 100644 --- a/gcloud/alpha/compute/images/update +++ b/gcloud/alpha/compute/images/update @@ -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, diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index ff8211b4b..595d4d2cc 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -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 diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/create b/gcloud/alpha/compute/network-firewall-policies/rules/create index 9ed7c41f0..745749766 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/create +++ b/gcloud/alpha/compute/network-firewall-policies/rules/create @@ -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. diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/update b/gcloud/alpha/compute/network-firewall-policies/rules/update index caccfcf21..6947fa93f 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/update +++ b/gcloud/alpha/compute/network-firewall-policies/rules/update @@ -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. diff --git a/gcloud/alpha/compute/os-config/troubleshoot b/gcloud/alpha/compute/os-config/troubleshoot index ed59fe262..e4aeb3826 100644 --- a/gcloud/alpha/compute/os-config/troubleshoot +++ b/gcloud/alpha/compute/os-config/troubleshoot @@ -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 diff --git a/gcloud/alpha/compute/security-policies/rules/create b/gcloud/alpha/compute/security-policies/rules/create index 420687af6..98d77f349 100644 --- a/gcloud/alpha/compute/security-policies/rules/create +++ b/gcloud/alpha/compute/security-policies/rules/create @@ -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. diff --git a/gcloud/alpha/compute/security-policies/rules/update b/gcloud/alpha/compute/security-policies/rules/update index 7aa44bd26..ca22fe6ef 100644 --- a/gcloud/alpha/compute/security-policies/rules/update +++ b/gcloud/alpha/compute/security-policies/rules/update @@ -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. diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index f2777f793..c3077aa2c 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -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. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 829be4a37..dfadb58fd 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -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. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 17839727d..5b5593c45 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -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. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 15b5c879e..b02b35d57 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -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. diff --git a/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac b/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac index 77102717e..e2cf1588e 100644 --- a/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac +++ b/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac @@ -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 diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register index d91e6f73c..316f31d10 100644 --- a/gcloud/alpha/container/fleet/memberships/register +++ b/gcloud/alpha/container/fleet/memberships/register @@ -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 diff --git a/gcloud/alpha/container/fleet/memberships/unregister b/gcloud/alpha/container/fleet/memberships/unregister index c6eec0d8b..5fe7a3108 100644 --- a/gcloud/alpha/container/fleet/memberships/unregister +++ b/gcloud/alpha/container/fleet/memberships/unregister @@ -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; diff --git a/gcloud/alpha/container/hub/memberships/generate-gateway-rbac b/gcloud/alpha/container/hub/memberships/generate-gateway-rbac index da6f8cec9..4a0128943 100644 --- a/gcloud/alpha/container/hub/memberships/generate-gateway-rbac +++ b/gcloud/alpha/container/hub/memberships/generate-gateway-rbac @@ -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 diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index ddf88edae..d51279448 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -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 diff --git a/gcloud/alpha/container/hub/memberships/unregister b/gcloud/alpha/container/hub/memberships/unregister index ae081dca2..585daf1d0 100644 --- a/gcloud/alpha/container/hub/memberships/unregister +++ b/gcloud/alpha/container/hub/memberships/unregister @@ -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; diff --git a/gcloud/alpha/deploy/releases/create b/gcloud/alpha/deploy/releases/create index 9dd68c68c..2a9a0f09b 100644 --- a/gcloud/alpha/deploy/releases/create +++ b/gcloud/alpha/deploy/releases/create @@ -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, diff --git a/gcloud/alpha/dns/dns-keys/list b/gcloud/alpha/dns/dns-keys/list index 5477f2aa0..95cfee9d5 100644 --- a/gcloud/alpha/dns/dns-keys/list +++ b/gcloud/alpha/dns/dns-keys/list @@ -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 diff --git a/gcloud/alpha/domains/registrations/help b/gcloud/alpha/domains/registrations/help index b258f8d24..c9dbaf5cd 100644 --- a/gcloud/alpha/domains/registrations/help +++ b/gcloud/alpha/domains/registrations/help @@ -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. diff --git a/gcloud/alpha/domains/registrations/import b/gcloud/alpha/domains/registrations/import new file mode 100644 index 000000000..ac3039fad --- /dev/null +++ b/gcloud/alpha/domains/registrations/import @@ -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 + diff --git a/gcloud/alpha/domains/registrations/list-importable-domains b/gcloud/alpha/domains/registrations/list-importable-domains new file mode 100644 index 000000000..95f1efd32 --- /dev/null +++ b/gcloud/alpha/domains/registrations/list-importable-domains @@ -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 + diff --git a/gcloud/alpha/functions/add-invoker-policy-binding b/gcloud/alpha/functions/add-invoker-policy-binding index 3300cc5ea..76a1539cc 100644 --- a/gcloud/alpha/functions/add-invoker-policy-binding +++ b/gcloud/alpha/functions/add-invoker-policy-binding @@ -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 diff --git a/gcloud/alpha/functions/list b/gcloud/alpha/functions/list index 504889f84..ad437ab10 100644 --- a/gcloud/alpha/functions/list +++ b/gcloud/alpha/functions/list @@ -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. diff --git a/gcloud/alpha/functions/remove-invoker-policy-binding b/gcloud/alpha/functions/remove-invoker-policy-binding index 21939d43b..cee307535 100644 --- a/gcloud/alpha/functions/remove-invoker-policy-binding +++ b/gcloud/alpha/functions/remove-invoker-policy-binding @@ -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 diff --git a/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding index 498477009..3bf5b74e7 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding +++ b/gcloud/alpha/iap/tcp/dest-groups/add-iam-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 diff --git a/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy index 368ab07f3..141f4a3da 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy +++ b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy @@ -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 diff --git a/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding index 175784d68..b5cd1ae1c 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding +++ b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding @@ -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 diff --git a/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy index 93616412b..bef7e3fb2 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy +++ b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy @@ -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 diff --git a/gcloud/alpha/logging/sinks/create b/gcloud/alpha/logging/sinks/create index c4a41d290..1b14a4650 100644 --- a/gcloud/alpha/logging/sinks/create +++ b/gcloud/alpha/logging/sinks/create @@ -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. diff --git a/gcloud/alpha/logging/sinks/update b/gcloud/alpha/logging/sinks/update index e5b547e6e..a3d5310be 100644 --- a/gcloud/alpha/logging/sinks/update +++ b/gcloud/alpha/logging/sinks/update @@ -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. diff --git a/gcloud/alpha/run/integrations/create b/gcloud/alpha/run/integrations/create index e0e7005cf..c51f49f50 100644 --- a/gcloud/alpha/run/integrations/create +++ b/gcloud/alpha/run/integrations/create @@ -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, diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 5c70f16b3..22a7dc93c 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -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,...] diff --git a/gcloud/anthos/config/controller/list b/gcloud/anthos/config/controller/list index 7c4880cc8..bae99a1ff 100644 --- a/gcloud/anthos/config/controller/list +++ b/gcloud/anthos/config/controller/list @@ -3,7 +3,7 @@ NAME instances SYNOPSIS - gcloud anthos config controller list [--location=LOCATION] + gcloud anthos config controller list [--full-name] [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -16,11 +16,19 @@ EXAMPLES $ gcloud anthos config controller list --location=us-central1 + To list all Anthos Config Controller instances in all regions with their + fully specified name, run: + + $ gcloud anthos config controller list --full-name + To list all Anthos Config Controller instances in all regions, run: $ gcloud 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 diff --git a/gcloud/artifacts/packages/describe b/gcloud/artifacts/packages/describe new file mode 100644 index 000000000..d4664c95f --- /dev/null +++ b/gcloud/artifacts/packages/describe @@ -0,0 +1,75 @@ +NAME + gcloud artifacts packages describe - describe an Artifact Registry package + +SYNOPSIS + gcloud artifacts packages describe + (PACKAGE : --location=LOCATION --repository=REPOSITORY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Artifact Registry package. + + This command can fail for the following reasons: + ▪ The specified package does not exist. + ▪ The active account does not have permission to view packages. + +EXAMPLES + To describe a package named my-pkg under the current project, repository, + and location, run: + + $ gcloud artifacts packages describe my-pkg + +POSITIONAL ARGUMENTS + Package resource - The Artifact Registry package to describe. 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 package on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + PACKAGE + ID of the package or fully qualified identifier for the package. To + set the package attribute: + ▸ provide the argument package on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the package. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument package on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the package. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument package on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +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. + +API REFERENCE + This command uses the artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/packages/help b/gcloud/artifacts/packages/help index ab3a075dc..5d81b3400 100644 --- a/gcloud/artifacts/packages/help +++ b/gcloud/artifacts/packages/help @@ -31,6 +31,9 @@ COMMANDS delete Delete an Artifact Registry package. + describe + Describe an Artifact Registry package. + list List Artifact Registry packages. diff --git a/gcloud/beta/ai/models/upload b/gcloud/beta/ai/models/upload index cf12ce93a..2de23074a 100644 --- a/gcloud/beta/ai/models/upload +++ b/gcloud/beta/ai/models/upload @@ -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, diff --git a/gcloud/beta/beyondcorp/app/connections/create b/gcloud/beta/beyondcorp/app/connections/create new file mode 100644 index 000000000..d3e01cef1 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/create @@ -0,0 +1,129 @@ +NAME + gcloud beta beyondcorp app connections create - create a new Beyondcorp + application connection + +SYNOPSIS + gcloud beta beyondcorp app connections create + (CONNECTION : --location=LOCATION) + (--application-endpoint=APPLICATION_ENDPOINT + | --application-endpoint-host=APPLICATION_ENDPOINT_HOST + --application-endpoint-port=APPLICATION_ENDPOINT_PORT) [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--type=TYPE; default="TCP_PROXY"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Beyondcorp application connection. + +EXAMPLES + The following command creates a Connection with ID my-connection using + default tcp type connection: + + $ gcloud beta beyondcorp app connections create my-connection \ + --location=us-central1 --application-endpoint=localhost:8080 + + The following command creates a Connection with ID my-connection with + explicit project value for all required and optional parameters: + + $ gcloud beta beyondcorp app connections create my-connection \ + --project=projectId --location=us-central1 \ + --application-endpoint-host=localhost \ + --application-endpoint-port=8080 --type=tcp \ + --connectors=my-connector1,my-connector2 --labels='foo=bar' \ + --display-name=connection-display-name --async + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp application connection you want to + create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Application endpoint. + + Exactly one of these must be specified: + + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --application-endpoint-host=APPLICATION_ENDPOINT_HOST + Hostname or IP address of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + + --application-endpoint-port=APPLICATION_ENDPOINT_PORT + Port of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors names that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --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. + + --type=TYPE; default="TCP_PROXY" + The type of network connnectivity used by the connection. TYPE must be + (currently only one value is supported): + + tcp + TCP connection + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections create + diff --git a/gcloud/beta/beyondcorp/app/connections/delete b/gcloud/beta/beyondcorp/app/connections/delete new file mode 100644 index 000000000..4e045f32f --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/delete @@ -0,0 +1,67 @@ +NAME + gcloud beta beyondcorp app connections delete - delete a single Connection + +SYNOPSIS + gcloud beta beyondcorp app connections delete + (CONNECTION : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a single Connection. + +EXAMPLES + To delete a connection named my-connection run: + + $ gcloud beta beyondcorp app connections delete my-connection \ + --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection you want to delete. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections delete + diff --git a/gcloud/beta/beyondcorp/app/connections/describe b/gcloud/beta/beyondcorp/app/connections/describe new file mode 100644 index 000000000..46c8a73db --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/describe @@ -0,0 +1,72 @@ +NAME + gcloud beta beyondcorp app connections describe - describe a single + Connection + +SYNOPSIS + gcloud beta beyondcorp app connections describe + (CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a single Connection. + +EXAMPLES + To describe a connection my-connection run: + + $ gcloud beta beyondcorp app connections describe my-connection \ + --project={project} --location=us-central1 + + To describe a connection my-connection in a project for location + us-central1 in table form, run: + + $ gcloud beta beyondcorp app connections describe my-connection \ + --project={project} --location=us-central1 \ + --format=table(displayName, name.basename(), state, \ + applicationEndpoint.host, applicationEndpoint.port, \ + updateTime, labels) + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connector you want to get details + about. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections describe + diff --git a/gcloud/beta/beyondcorp/app/connections/help b/gcloud/beta/beyondcorp/app/connections/help new file mode 100644 index 000000000..1e48d0109 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/help @@ -0,0 +1,42 @@ +NAME + gcloud beta beyondcorp app connections - create and manipulate beyondcorp + connections + +SYNOPSIS + gcloud beta beyondcorp app connections COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) A Beyondcorp Connection resource represents a BeyondCorp protected + connection to a remote application. It creates all the necessary Google + Cloud Platform components needed for creating a BeyondCorp protected + connection. Multiple connectors can be authorised for a single Connection. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new Beyondcorp application connection. + + delete + (BETA) Delete a single Connection. + + describe + (BETA) Describe a single Connection. + + list + (BETA) List Beyondcorp connection Resources. + + update + (BETA) Update an existing Beyondcorp application connection. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections + diff --git a/gcloud/beta/beyondcorp/app/connections/list b/gcloud/beta/beyondcorp/app/connections/list new file mode 100644 index 000000000..76a555560 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/list @@ -0,0 +1,88 @@ +NAME + gcloud beta beyondcorp app connections list - list Beyondcorp connection + Resources + +SYNOPSIS + gcloud beta beyondcorp app connections list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Beyondcorp connection resources based on project and location. + +EXAMPLES + To list all connections in a project for location us-central1 in table + form, run: + + $ gcloud beta beyondcorp app connections list --project=projectId \ + --location=us-central1 + + To list all connections in a project for location us-central1 in json form, + run: + + $ gcloud beta beyondcorp app connections list --project=projectId \ + --location=us-central1 --format=json(displayName, \ + name.basename(), state, applicationEndpoint.host, \ + applicationEndpoint.port, updateTime, labels) + +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections list + diff --git a/gcloud/beta/beyondcorp/app/connections/update b/gcloud/beta/beyondcorp/app/connections/update new file mode 100644 index 000000000..b50330f55 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connections/update @@ -0,0 +1,117 @@ +NAME + gcloud beta beyondcorp app connections update - update an existing + Beyondcorp application connection + +SYNOPSIS + gcloud beta beyondcorp app connections update + (CONNECTION : --location=LOCATION) + [--application-endpoint=APPLICATION_ENDPOINT] [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing Beyondcorp application connection. + +EXAMPLES + To modify the connection my-connection in 'us-central1' by adding labels + 'k0', with value 'value1' and label 'k1' with value 'value2' and removing + labels with key 'k3', run: + + $ gcloud beta beyondcorp app connections update my-connection \ + --location=us-central1 --display-name=new-display-name \ + --connectors={connector1} --application-endpoint=host:port \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection you want to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors names that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + 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. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta beyondcorp app connections update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta beyondcorp app connections update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connections update + diff --git a/gcloud/beta/beyondcorp/app/connectors/create b/gcloud/beta/beyondcorp/app/connectors/create new file mode 100644 index 000000000..e1622c99f --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/create @@ -0,0 +1,98 @@ +NAME + gcloud beta beyondcorp app connectors create - create a new Beyondcorp + application connector + +SYNOPSIS + gcloud beta beyondcorp app connectors create + (CONNECTOR : --location=LOCATION) --member=MEMBER [--async] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Beyondcorp application connector. + +EXAMPLES + The following command creates a Connector with ID my-connector in the + default user project: + + $ gcloud beta beyondcorp app connectors create my-connector \ + --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com + + The following command creates a Connector with ID my-connector with + explicit project value for all required and optional parameters: + + $ gcloud beta beyondcorp app connectors create my-connector \ + --project=projectId --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com --labels='foo=bar' --display-name=connector-display-name \ + --async + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to create. 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=MEMBER + Connector service account email in form of 'serviceAccount:email'. + +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 connector. Cannot exceed 64 + characters. + + --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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors create + diff --git a/gcloud/beta/beyondcorp/app/connectors/delete b/gcloud/beta/beyondcorp/app/connectors/delete new file mode 100644 index 000000000..81b291136 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/delete @@ -0,0 +1,67 @@ +NAME + gcloud beta beyondcorp app connectors delete - delete a single Connector + +SYNOPSIS + gcloud beta beyondcorp app connectors delete + (CONNECTOR : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a single Connector. + +EXAMPLES + To delete a connector my-connector run: + + $ gcloud beta beyondcorp app connectors delete my-connector \ + --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to delete. 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors delete + diff --git a/gcloud/beta/beyondcorp/app/connectors/describe b/gcloud/beta/beyondcorp/app/connectors/describe new file mode 100644 index 000000000..e8b4a6a88 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/describe @@ -0,0 +1,75 @@ +NAME + gcloud beta beyondcorp app connectors describe - describe a single + Connector + +SYNOPSIS + gcloud beta beyondcorp app connectors describe + (CONNECTOR : --location=LOCATION) [--details] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a single Connector. + +EXAMPLES + To describe a connector my-connector run: + + $ gcloud beta beyondcorp app connectors describe my-connector \ + --project={project} --location={location} + + To describe a connector in a project for location us-central1 in table + form, run: + + $ gcloud beta beyondcorp app connectors describe \ + --project=projectId --location=us-central1 \ + --format=table(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to get details + about. 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --details + Includes details. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors describe + diff --git a/gcloud/beta/beyondcorp/app/connectors/help b/gcloud/beta/beyondcorp/app/connectors/help new file mode 100644 index 000000000..c0f957d7d --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/help @@ -0,0 +1,43 @@ +NAME + gcloud beta beyondcorp app connectors - create and manipulate beyondcorp + connectors + +SYNOPSIS + gcloud beta beyondcorp app connectors COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) A Beyondcorp connector represents an application facing component + deployed proximal to and with direct access to the application instances. + It is used to establish connectivity between the remote enterprise + environment and Google Cloud Platform. It initiates connections to the + applications and can proxy the data from users over the connection. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new Beyondcorp application connector. + + delete + (BETA) Delete a single Connector. + + describe + (BETA) Describe a single Connector. + + list + (BETA) List Beyondcorp connector Resources. + + update + (BETA) Update an existing Beyondcorp application connector. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors + diff --git a/gcloud/beta/beyondcorp/app/connectors/list b/gcloud/beta/beyondcorp/app/connectors/list new file mode 100644 index 000000000..507858cc1 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/list @@ -0,0 +1,87 @@ +NAME + gcloud beta beyondcorp app connectors list - list Beyondcorp connector + Resources + +SYNOPSIS + gcloud beta beyondcorp app connectors list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Beyondcorp connector resources based on project and location. + +EXAMPLES + To list all connectors in a project for location us-central1 in table form, + run: + + $ gcloud beta beyondcorp app connectors list --project=projectId \ + --location=us-central1 + + To list all connectors in a project for location us-central1 in json form, + run: + + $ gcloud beta beyondcorp app connectors list --project=projectId \ + --location=us-central1 --format=json(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) + +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors list + diff --git a/gcloud/beta/beyondcorp/app/connectors/update b/gcloud/beta/beyondcorp/app/connectors/update new file mode 100644 index 000000000..f2cb80ab1 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/connectors/update @@ -0,0 +1,106 @@ +NAME + gcloud beta beyondcorp app connectors update - update an existing + Beyondcorp application connector + +SYNOPSIS + gcloud beta beyondcorp app connectors update + (CONNECTOR : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing Beyondcorp application connector. + +EXAMPLES + To modify the connector my-connector in 'us-central1' by adding labels + 'k0', with value 'value1' and label 'k1' with value 'value2' and removing + labels with key 'k3', run: + + $ gcloud beta beyondcorp app connectors update my-connector \ + --location=us-central1 --display-name=new-display-name \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to update 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connector. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + 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. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta beyondcorp app connectors update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta beyondcorp app connectors update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app connectors update + diff --git a/gcloud/beta/beyondcorp/app/help b/gcloud/beta/beyondcorp/app/help new file mode 100644 index 000000000..bae551f78 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/help @@ -0,0 +1,43 @@ +NAME + gcloud beta beyondcorp app - manages application connectors and connections + +SYNOPSIS + gcloud beta beyondcorp app GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud beyondcorp command group lets you secure non-gcp + application by managing connectors and connections. + + BeyondCorp Enterprise offers a zero trust solution that enables secure + access with integrated threat and data protection.The solution enables + secure access to both Google Cloud Platform and on-prem hosted apps. For + remote apps that are not deployed in Google Cloud Platform, BeyondCorp + Enterprise's App connector provides simplified connectivity and app + publishing experience. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + connections + (BETA) Create and manipulate beyondcorp connections. + + connectors + (BETA) Create and manipulate beyondcorp connectors. + + operations + (BETA) List and Describe beyondcorp appconnector operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app + diff --git a/gcloud/beta/beyondcorp/app/operations/describe b/gcloud/beta/beyondcorp/app/operations/describe new file mode 100644 index 000000000..cc176f32c --- /dev/null +++ b/gcloud/beta/beyondcorp/app/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta beyondcorp app operations describe - describe a Beyondcorp + Appconnector operation + +SYNOPSIS + gcloud beta beyondcorp app operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Beyondcorp Appconnector operation given a valid operation + name. + +EXAMPLES + The following command describes an operation called + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9: + + $ gcloud beta beyondcorp app operations describe \ + --location=us-central1 \ + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9 + +POSITIONAL ARGUMENTS + Operation resource - Name of the AppConnector operation you want to + describe. 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 operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app operations describe + diff --git a/gcloud/beta/beyondcorp/app/operations/help b/gcloud/beta/beyondcorp/app/operations/help new file mode 100644 index 000000000..410ce49a7 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/operations/help @@ -0,0 +1,30 @@ +NAME + gcloud beta beyondcorp app operations - list and Describe beyondcorp + appconnector operations + +SYNOPSIS + gcloud beta beyondcorp app operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List and Describe beyondcorp appconnector operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a Beyondcorp Appconnector operation. + + list + (BETA) List Beyondcorp Appconnector operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app operations + diff --git a/gcloud/beta/beyondcorp/app/operations/list b/gcloud/beta/beyondcorp/app/operations/list new file mode 100644 index 000000000..56a9aa157 --- /dev/null +++ b/gcloud/beta/beyondcorp/app/operations/list @@ -0,0 +1,82 @@ +NAME + gcloud beta beyondcorp app operations list - list Beyondcorp Appconnector + operations + +SYNOPSIS + gcloud beta beyondcorp app operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Beyondcorp Appconnector operations in the specified + project. + + You can specify the maximum number of operations to list using the --limit + flag. + +EXAMPLES + The following command lists a maximum of five operations: + + $ gcloud beta beyondcorp app operations list \ + --location=us-central1 --limit=5 + +REQUIRED FLAGS + Location resource - Region of the operations to display. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp app operations list + diff --git a/gcloud/beta/beyondcorp/client-connector/gateways/create b/gcloud/beta/beyondcorp/client-connector/gateways/create new file mode 100644 index 000000000..6767e38d4 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/gateways/create @@ -0,0 +1,88 @@ +NAME + gcloud beta beyondcorp client-connector gateways create - create a new + BeyondCorp client gateway + +SYNOPSIS + gcloud beta beyondcorp client-connector gateways create + (CLIENT_GATEWAY : --location=LOCATION) + --client-connector-service=CLIENT_CONNECTOR_SERVICE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new BeyondCorp client gateway. + +EXAMPLES + The following command creates a client gateway with ID my-client-gateway in + the default user project and location us-central1: + + $ gcloud beta beyondcorp client-connector gateways create \ + my-client-gateway --location=us-central1 \ + --client-connector-service=projects/consumer-project-id/\ + locations/us-central1/clientConnectorServices/my-service-resource + + The following command creates a client gateway with ID my-client-gateway + with explicit values for all required and optional parameters: + + $ gcloud beta beyondcorp client-connector gateways create \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 \ + --client-connector-service=projects/consumer-project-id/\ + locations/us-central1/clientConnectorServices/my-service-resource + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway you want to + create. 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --client-connector-service=CLIENT_CONNECTOR_SERVICE + The client connector service that the client gateway is associated + with. Example - + projects/consumer-project-id/locations/us-central1/clientConnectorServices/my-service-resource. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector gateways create + diff --git a/gcloud/beta/beyondcorp/client-connector/gateways/delete b/gcloud/beta/beyondcorp/client-connector/gateways/delete new file mode 100644 index 000000000..25e6dbca2 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/gateways/delete @@ -0,0 +1,69 @@ +NAME + gcloud beta beyondcorp client-connector gateways delete - delete a single + BeyondCorp client gateway + +SYNOPSIS + gcloud beta beyondcorp client-connector gateways delete + (CLIENT_GATEWAY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a single BeyondCorp client gateway. + +EXAMPLES + To delete a client gateway with ID my-client-gateway run: + + $ gcloud beta beyondcorp client-connector gateways delete \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway you want to + delete. 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector gateways delete + diff --git a/gcloud/beta/beyondcorp/client-connector/gateways/describe b/gcloud/beta/beyondcorp/client-connector/gateways/describe new file mode 100644 index 000000000..551cc1d14 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/gateways/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta beyondcorp client-connector gateways describe - describe a + single BeyondCorp client gateway + +SYNOPSIS + gcloud beta beyondcorp client-connector gateways describe + (CLIENT_GATEWAY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a single BeyondCorp client gateway. + +EXAMPLES + To describe a client gateway my-client-gateway run: + + $ gcloud beta beyondcorp client-connector gateways describe \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway you want to get + details about. 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector gateways describe + diff --git a/gcloud/beta/beyondcorp/client-connector/gateways/help b/gcloud/beta/beyondcorp/client-connector/gateways/help new file mode 100644 index 000000000..f6bbf19a3 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/gateways/help @@ -0,0 +1,42 @@ +NAME + gcloud beta beyondcorp client-connector gateways - create and manipulate + BeyondCorp client gateways + +SYNOPSIS + gcloud beta beyondcorp client-connector gateways COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Regional, server-side components to which clients can connect. + Client gateways are deployed by administrators. The gateways communicate + with the BeyondCorp Enterprise enforcement system to enforce context-aware + checks. The BeyondCorp Enterprise enforcement system uses Identity-Aware + Proxy and Access Context Manager, a flexible BeyondCorp Enterprise zero + trust policy engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new BeyondCorp client gateway. + + delete + (BETA) Delete a single BeyondCorp client gateway. + + describe + (BETA) Describe a single BeyondCorp client gateway. + + list + (BETA) List BeyondCorp client gateway resources. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector gateways + diff --git a/gcloud/beta/beyondcorp/client-connector/gateways/list b/gcloud/beta/beyondcorp/client-connector/gateways/list new file mode 100644 index 000000000..a84c7c3af --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/gateways/list @@ -0,0 +1,81 @@ +NAME + gcloud beta beyondcorp client-connector gateways list - list BeyondCorp + client gateway resources + +SYNOPSIS + gcloud beta beyondcorp client-connector gateways list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List BeyondCorp client gateway resources based on project and + location. + +EXAMPLES + To list all client gateways in a project for location us-central1 in table + form, run: + + $ gcloud beta beyondcorp client-connector gateways list \ + --project=consumer-project-id --location=us-central1 + +REQUIRED FLAGS + Location resource - Arguments and flags that define the BeyondCorp client + gateways you want to list. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector gateways list + diff --git a/gcloud/beta/beyondcorp/client-connector/help b/gcloud/beta/beyondcorp/client-connector/help new file mode 100644 index 000000000..05e5aefbe --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/help @@ -0,0 +1,44 @@ +NAME + gcloud beta beyondcorp client-connector - provides context-aware access to + non-web applications + +SYNOPSIS + gcloud beta beyondcorp client-connector GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) BeyondCorp Enterprise is the zero trust solution from Google that + provides secure access to private applications with integrated threat and + data protection. BeyondCorp Enterprise uses Chrome to provide secure access + for all web-based (HTTPS) applications. + + The BeyondCorp Enterprise client connector extends support to non-web + applications by creating a secure connection to applications running in + both Google Cloud and non-Google Cloud environments with full context and + identity aware access. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp-enterprise/docs/client-connector + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + gateways + (BETA) Create and manipulate BeyondCorp client gateways. + + operations + (BETA) List and describe BeyondCorp client connector operations. + + services + (BETA) Create and manipulate BeyondCorp client connector services. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector + diff --git a/gcloud/beta/beyondcorp/client-connector/operations/describe b/gcloud/beta/beyondcorp/client-connector/operations/describe new file mode 100644 index 000000000..d26d64297 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta beyondcorp client-connector operations describe - describe a + BeyondCorp client connector operation + +SYNOPSIS + gcloud beta beyondcorp client-connector operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a BeyondCorp client connector operation given a valid + operation name. + +EXAMPLES + The following command describes an operation called + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9: + + $ gcloud beta beyondcorp client-connector operations describe \ + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9 \ + --project=consumer-project-id --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - Name of the client connector operation you want to + describe. 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 operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector operations describe + diff --git a/gcloud/beta/beyondcorp/client-connector/operations/help b/gcloud/beta/beyondcorp/client-connector/operations/help new file mode 100644 index 000000000..730e3d322 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/operations/help @@ -0,0 +1,31 @@ +NAME + gcloud beta beyondcorp client-connector operations - list and describe + BeyondCorp client connector operations + +SYNOPSIS + gcloud beta beyondcorp client-connector operations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List and describe BeyondCorp client connector operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a BeyondCorp client connector operation. + + list + (BETA) List BeyondCorp client connector operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector operations + diff --git a/gcloud/beta/beyondcorp/client-connector/operations/list b/gcloud/beta/beyondcorp/client-connector/operations/list new file mode 100644 index 000000000..a1c11fca5 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/operations/list @@ -0,0 +1,82 @@ +NAME + gcloud beta beyondcorp client-connector operations list - list BeyondCorp + client connector operations + +SYNOPSIS + gcloud beta beyondcorp client-connector operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all BeyondCorp client connector operations in the specified + project. + + You can specify the maximum number of operations to list using the --limit + flag. + +EXAMPLES + The following command lists a maximum of five operations: + + $ gcloud beta beyondcorp client-connector operations list \ + --project=consumer-project-id --location=us-central1 --limit=5 + +REQUIRED FLAGS + Location resource - Location of the operations to display. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector operations list + diff --git a/gcloud/beta/beyondcorp/client-connector/services/create b/gcloud/beta/beyondcorp/client-connector/services/create new file mode 100644 index 000000000..033d0068c --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/create @@ -0,0 +1,139 @@ +NAME + gcloud beta beyondcorp client-connector services create - create a new + BeyondCorp client connector service + +SYNOPSIS + gcloud beta beyondcorp client-connector services create + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) + (--config-from-file=CONFIG_FROM_FILE + | [--egress-peered-vpc=EGRESS_PEERED_VPC + --ingress-config=INGRESS_CONFIG : --display-name=DISPLAY_NAME]) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new BeyondCorp client connector service. + +EXAMPLES + The following command creates a client connector service with ID + my-service-resource using ingress/egress config provided: + + $ gcloud beta beyondcorp client-connector services create \ + my-service-resource --location=us-central1 \ + --project=consumer-project-id \ + --ingress-config='{"transportProtocol":"TCP", + "destinationRoutes":[{"address":"196.0.0.1", + "netmask":"255.255.255.0"}]}' \ + --egress-peered-vpc='{"networkVpc":"projects/consumer-project-id\ + /global/networks/my-vpc-network"}' + + The following command creates a client connector service with ID + my-service-resource with configuration from file: + + $ gcloud beta beyondcorp client-connector services create \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 \ + --config-from-file=/path/to/file/configJson.txt + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service you want to create. 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Client connector service configuration. + + Exactly one of these must be specified: + + --config-from-file=CONFIG_FROM_FILE + Path to json file containing client connector service configuration. + Example - "/file/path/configJson.txt" where configJson.txt contains - { + "ingress":{ + "config":{ + "transportProtocol":"TCP", + "destinationRoutes":[{ + "address":"196.0.0.1", + "netmask":"255.255.255.0" + }] + } + }, + "egress":{ + "peeredVpc":{ + "networkVpc":"projects/consumer-project-id/global/networks/my-vpc-network" + } + }, + "displayName":"my-service-resource" + } + + --egress-peered-vpc=EGRESS_PEERED_VPC + The peered VPC owned by the consumer project. Example - + {"networkVpc": + "projects/consumer-project-id/global/networks/my-vpc-network"}. + + This flag must be specified if any of the other arguments in this + group are specified. + + --ingress-config=INGRESS_CONFIG + The basic ingress config for client gateways. Example - + {"transportProtocol": + "TCP","destinationRoutes":[{"address":"196.0.0.1", + "netmask":"255.255.255.0"}]}. + + This flag must be specified if any of the other arguments in this + group are specified. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the client connector service. The + display name should follow format - + ▸ Must be 6 to 30 characters in length. + ▸ Can only contain lowercase letters, numbers and hyphens. + ▸ Must start with a letter. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services create + diff --git a/gcloud/beta/beyondcorp/client-connector/services/delete b/gcloud/beta/beyondcorp/client-connector/services/delete new file mode 100644 index 000000000..d88c1d9c8 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/delete @@ -0,0 +1,73 @@ +NAME + gcloud beta beyondcorp client-connector services delete - delete a + BeyondCorp client connector service + +SYNOPSIS + gcloud beta beyondcorp client-connector services delete + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a BeyondCorp client connector service. + +EXAMPLES + To delete a client connector service with ID my-service-resource run: + + $ gcloud beta beyondcorp client-connector services delete \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service you want to delete. 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services delete + diff --git a/gcloud/beta/beyondcorp/client-connector/services/describe b/gcloud/beta/beyondcorp/client-connector/services/describe new file mode 100644 index 000000000..baa7aff32 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta beyondcorp client-connector services describe - describe a + BeyondCorp client connector service + +SYNOPSIS + gcloud beta beyondcorp client-connector services describe + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a BeyondCorp client connector service. + +EXAMPLES + To describe a client connector service with ID my-service-resource run: + + $ gcloud beta beyondcorp client-connector services describe \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service you want to get details about. 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services describe + diff --git a/gcloud/beta/beyondcorp/client-connector/services/help b/gcloud/beta/beyondcorp/client-connector/services/help new file mode 100644 index 000000000..26dfa907b --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/help @@ -0,0 +1,47 @@ +NAME + gcloud beta beyondcorp client-connector services - create and manipulate + BeyondCorp client connector services + +SYNOPSIS + gcloud beta beyondcorp client-connector services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The client connector service is used to define a common + configuration for a group of client gateways. Client gateways refer to the + client connector service and are used to control the regions where you want + to manage user traffic. The gateways communicate with the BeyondCorp + Enterprise enforcement system to enforce context-aware checks. The + BeyondCorp Enterprise enforcement system uses Identity-Aware Proxy and + Access Context Manager, a flexible BeyondCorp Enterprise zero trust policy + engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new BeyondCorp client connector service. + + delete + (BETA) Delete a BeyondCorp client connector service. + + describe + (BETA) Describe a BeyondCorp client connector service. + + list + (BETA) List BeyondCorp client connector service resources. + + update + (BETA) Update a BeyondCorp client connector service. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services + diff --git a/gcloud/beta/beyondcorp/client-connector/services/list b/gcloud/beta/beyondcorp/client-connector/services/list new file mode 100644 index 000000000..0a1647c15 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/list @@ -0,0 +1,87 @@ +NAME + gcloud beta beyondcorp client-connector services list - list BeyondCorp + client connector service resources + +SYNOPSIS + gcloud beta beyondcorp client-connector services list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List BeyondCorp client connector service resources based on project + and location. + +EXAMPLES + To list all client connector services in a project for location us-central1 + in table form, run: + + $ gcloud beta beyondcorp client-connector services list \ + --project=consumer-project-id --location=us-central1 + + To list all client connector service in a project for location us-central1 + with limit=1, run: + + $ gcloud beta beyondcorp client-connector services list \ + --project=consumer-project-id --location=us-central1 --limit=1 + +REQUIRED FLAGS + Location resource - Arguments and flags that define the BeyondCorp client + connector services you want to list. 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 --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services list + diff --git a/gcloud/beta/beyondcorp/client-connector/services/update b/gcloud/beta/beyondcorp/client-connector/services/update new file mode 100644 index 000000000..43b0c36d3 --- /dev/null +++ b/gcloud/beta/beyondcorp/client-connector/services/update @@ -0,0 +1,81 @@ +NAME + gcloud beta beyondcorp client-connector services update - update a + BeyondCorp client connector service + +SYNOPSIS + gcloud beta beyondcorp client-connector services update + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a BeyondCorp client connector service. + +EXAMPLES + The following command updates a client connector service with ID + my-service-resource in location us-central1: + + $ gcloud beta beyondcorp client-connector services update \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 --display-name="my-new-resource" + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service you want to update. 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the client connector service. The + display name should follow format - + ◆ Must be 6 to 30 characters in length. + ◆ Can only contain lowercase letters, numbers and hyphens. + ◆ Must start with a letter. + +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. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp client-connector services update + diff --git a/gcloud/beta/beyondcorp/help b/gcloud/beta/beyondcorp/help new file mode 100644 index 000000000..cc1195a30 --- /dev/null +++ b/gcloud/beta/beyondcorp/help @@ -0,0 +1,41 @@ +NAME + gcloud beta beyondcorp - manage secure access to applications with + integrated threat and data protection + +SYNOPSIS + gcloud beta beyondcorp GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) BeyondCorp Enterprise offers a zero trust solution that enables + secure access with integrated threat and data protection.The solution + enables secure access to both Google Cloud Platform and on-prem hosted + apps. For remote apps that are not deployed in Google Cloud Platform, + BeyondCorp Enterprise's App connector provides simplified connectivity and + app publishing experience. The BeyondCorp Enterprise client connector + extends support to non-web applications by creating a secure connection to + applications running in both Google Cloud and non-Google Cloud environments + with full context and identity aware access. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + app + (BETA) Manages application connectors and connections. + + client-connector + (BETA) Provides context-aware access to non-web applications. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha beyondcorp + diff --git a/gcloud/beta/compute/images/update b/gcloud/beta/compute/images/update index 74ec7f7c5..8dc545507 100644 --- a/gcloud/beta/compute/images/update +++ b/gcloud/beta/compute/images/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta compute images update IMAGE_NAME [--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 (BETA) gcloud beta compute images update updates labels for a Compute @@ -69,6 +71,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, diff --git a/gcloud/beta/compute/security-policies/rules/create b/gcloud/beta/compute/security-policies/rules/create index 0aa595842..13f907f39 100644 --- a/gcloud/beta/compute/security-policies/rules/create +++ b/gcloud/beta/compute/security-policies/rules/create @@ -55,6 +55,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. diff --git a/gcloud/beta/compute/security-policies/rules/update b/gcloud/beta/compute/security-policies/rules/update index 5d31d0454..b7553cf47 100644 --- a/gcloud/beta/compute/security-policies/rules/update +++ b/gcloud/beta/compute/security-policies/rules/update @@ -55,6 +55,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. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index a9488f3a7..8e9ac7482 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -71,9 +71,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. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 311fe1344..d84dd554b 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -103,9 +103,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. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index a0f42a49e..6fadf13d0 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -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. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 43512a91c..dc32a7b87 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -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. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 598b09b94..a5f7f5e55 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -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. diff --git a/gcloud/beta/container/fleet/memberships/generate-gateway-rbac b/gcloud/beta/container/fleet/memberships/generate-gateway-rbac index 35748a848..8e0ce3a24 100644 --- a/gcloud/beta/container/fleet/memberships/generate-gateway-rbac +++ b/gcloud/beta/container/fleet/memberships/generate-gateway-rbac @@ -111,8 +111,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships generate-gateway-rbac $ gcloud alpha container fleet memberships generate-gateway-rbac diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register index f6c54f345..2b4b45ec1 100644 --- a/gcloud/beta/container/fleet/memberships/register +++ b/gcloud/beta/container/fleet/memberships/register @@ -174,9 +174,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 diff --git a/gcloud/beta/container/hub/memberships/generate-gateway-rbac b/gcloud/beta/container/hub/memberships/generate-gateway-rbac index ce73b36a7..fbc2afc50 100644 --- a/gcloud/beta/container/hub/memberships/generate-gateway-rbac +++ b/gcloud/beta/container/hub/memberships/generate-gateway-rbac @@ -111,8 +111,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub memberships generate-gateway-rbac $ gcloud alpha container hub memberships generate-gateway-rbac diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 6c9d347a9..51383cfc2 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -174,9 +174,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 diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index c46ec3dec..cc4d77c6f 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -8,8 +8,7 @@ SYNOPSIS | --backfill-all --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS) (--destination-name=DESTINATION_NAME - (--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - | --gcs-destination-config=GCS_DESTINATION_CONFIG)) + --gcs-destination-config=GCS_DESTINATION_CONFIG) (--source-name=SOURCE_NAME (--mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG)) [--labels=[KEY=VALUE,...]] [--force | --validate-only] @@ -109,37 +108,21 @@ REQUIRED FLAGS connection_profile. To set the connection_profile attribute: ▫ provide the argument --destination-name on the command line. - Exactly one of these must be specified: + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. - --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for - Google BigQuery Destination Config. + The JSON file is formatted as follows: - The JSON file is formatted as follows: + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } - { - "source_hierarchy_datasets": { - "dataset_template": { - "location": "us-central1", - "dataset_id_prefix": "my_prefix", - "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" - } - }, - "data_freshness": 3600 - } - - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for - Google Cloud Storage Destination Config. - - The JSON file is formatted as follows: - - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + This flag must be specified if any of the other arguments in this + group are specified. This must be specified. diff --git a/gcloud/beta/datastream/streams/update b/gcloud/beta/datastream/streams/update index a9dcb8b41..c1a6368ef 100644 --- a/gcloud/beta/datastream/streams/update +++ b/gcloud/beta/datastream/streams/update @@ -10,8 +10,7 @@ SYNOPSIS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS] [--clear-labels | --remove-labels=[KEY,...]] [--destination-name=DESTINATION_NAME - : --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - | --gcs-destination-config=GCS_DESTINATION_CONFIG] + : --gcs-destination-config=GCS_DESTINATION_CONFIG] [--force | --validate-only] [--source-name=SOURCE_NAME : --mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG] [GCLOUD_WIDE_FLAG ...] @@ -145,37 +144,18 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --destination-name on the command line. - At most one of these can be specified: + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. - --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - BigQuery Destination Config. + The JSON file is formatted as follows: - The JSON file is formatted as follows: - - { - "source_hierarchy_datasets": { - "dataset_template": { - "location": "us-central1", - "dataset_id_prefix": "my_prefix", - "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" - } - }, - "data_freshness": 3600 - } - - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. - - The JSON file is formatted as follows: - - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } At most one of these can be specified: diff --git a/gcloud/beta/deploy/releases/create b/gcloud/beta/deploy/releases/create index bae0e1345..edeadfded 100644 --- a/gcloud/beta/deploy/releases/create +++ b/gcloud/beta/deploy/releases/create @@ -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 beta 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 beta 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 beta 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, diff --git a/gcloud/beta/dns/dns-keys/list b/gcloud/beta/dns/dns-keys/list index 6edb167b8..08c434153 100644 --- a/gcloud/beta/dns/dns-keys/list +++ b/gcloud/beta/dns/dns-keys/list @@ -15,8 +15,8 @@ EXAMPLES To see the DS records for every key-signing DnsKey in a managed zone, run: - $ gcloud beta dns dns-keys list --zone=my_zone 3 \ - --format='value(ds_record())' --filter='type=keySigning' + $ gcloud beta dns dns-keys list --zone=my_zone \ + --filter='type=keySigning' --format='value(ds_record())' REQUIRED FLAGS --zone=ZONE, -z ZONE diff --git a/gcloud/beta/domains/registrations/help b/gcloud/beta/domains/registrations/help index 07421ceb9..7d5536d36 100644 --- a/gcloud/beta/domains/registrations/help +++ b/gcloud/beta/domains/registrations/help @@ -44,9 +44,15 @@ COMMANDS get-transfer-parameters (BETA) Get transfer parameters of a specific domain. + import + (BETA) Import a domain from Google Domains registrar to Cloud Domains. + list (BETA) List Cloud Domains registrations. + list-importable-domains + (BETA) List Google Domains registrations importable into Cloud Domains. + register (BETA) Register a new domain. diff --git a/gcloud/beta/domains/registrations/import b/gcloud/beta/domains/registrations/import new file mode 100644 index 000000000..4d75d9426 --- /dev/null +++ b/gcloud/beta/domains/registrations/import @@ -0,0 +1,74 @@ +NAME + gcloud beta domains registrations import - import a domain from Google + Domains registrar to Cloud Domains + +SYNOPSIS + gcloud beta domains registrations import REGISTRATION [--async] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) 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 beta 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 beta and might change without notice. These + variants are also available: + + $ gcloud domains registrations import + + $ gcloud alpha domains registrations import + diff --git a/gcloud/beta/domains/registrations/list-importable-domains b/gcloud/beta/domains/registrations/list-importable-domains new file mode 100644 index 000000000..8324030d7 --- /dev/null +++ b/gcloud/beta/domains/registrations/list-importable-domains @@ -0,0 +1,69 @@ +NAME + gcloud beta domains registrations list-importable-domains - list Google + Domains registrations importable into Cloud Domains + +SYNOPSIS + gcloud beta domains registrations list-importable-domains + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) 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 beta 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 beta and might change without notice. These + variants are also available: + + $ gcloud domains registrations list-importable-domains + + $ gcloud alpha domains registrations list-importable-domains + diff --git a/gcloud/beta/functions/add-invoker-policy-binding b/gcloud/beta/functions/add-invoker-policy-binding index f134893ba..46623c4fe 100644 --- a/gcloud/beta/functions/add-invoker-policy-binding +++ b/gcloud/beta/functions/add-invoker-policy-binding @@ -69,8 +69,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud functions add-invoker-policy-binding $ gcloud alpha functions add-invoker-policy-binding diff --git a/gcloud/beta/functions/list b/gcloud/beta/functions/list index db13d33cc..61adba5fa 100644 --- a/gcloud/beta/functions/list +++ b/gcloud/beta/functions/list @@ -2,21 +2,14 @@ NAME gcloud beta functions list - list Google Cloud Functions SYNOPSIS - gcloud beta functions list [--gen2] - [--regions=REGION,[REGION,...]; default="-"] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud beta functions list [--regions=REGION,[REGION,...]; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) 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. diff --git a/gcloud/beta/functions/remove-invoker-policy-binding b/gcloud/beta/functions/remove-invoker-policy-binding index e035061bd..577e8b46c 100644 --- a/gcloud/beta/functions/remove-invoker-policy-binding +++ b/gcloud/beta/functions/remove-invoker-policy-binding @@ -73,8 +73,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud functions remove-invoker-policy-binding $ gcloud alpha functions remove-invoker-policy-binding diff --git a/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding b/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding index dd72b37b9..e42ed4120 100644 --- a/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding +++ b/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta 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 beta 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 beta 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 diff --git a/gcloud/beta/iap/tcp/dest-groups/get-iam-policy b/gcloud/beta/iap/tcp/dest-groups/get-iam-policy index bb11ee0d6..2aae21d6f 100644 --- a/gcloud/beta/iap/tcp/dest-groups/get-iam-policy +++ b/gcloud/beta/iap/tcp/dest-groups/get-iam-policy @@ -3,7 +3,7 @@ NAME TCP Destination Group resource SYNOPSIS - gcloud beta iap tcp dest-groups get-iam-policy --group-name=GROUP_NAME + gcloud beta 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 beta 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 beta 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 diff --git a/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding b/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding index ad9ffe455..930c8c685 100644 --- a/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding +++ b/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta 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 beta 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 beta 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 beta 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 diff --git a/gcloud/beta/iap/tcp/dest-groups/set-iam-policy b/gcloud/beta/iap/tcp/dest-groups/set-iam-policy index 1363339f4..df8bb006e 100644 --- a/gcloud/beta/iap/tcp/dest-groups/set-iam-policy +++ b/gcloud/beta/iap/tcp/dest-groups/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta 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 (BETA) This command replaces the existing IAM policy for an IAP TCP @@ -22,20 +22,21 @@ EXAMPLES run: $ gcloud beta 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 beta 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 diff --git a/gcloud/compute/security-policies/rules/create b/gcloud/compute/security-policies/rules/create index a146fa0eb..dcc468b91 100644 --- a/gcloud/compute/security-policies/rules/create +++ b/gcloud/compute/security-policies/rules/create @@ -55,6 +55,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. diff --git a/gcloud/compute/security-policies/rules/update b/gcloud/compute/security-policies/rules/update index 37ec11881..d92e800a8 100644 --- a/gcloud/compute/security-policies/rules/update +++ b/gcloud/compute/security-policies/rules/update @@ -55,6 +55,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. diff --git a/gcloud/config/get b/gcloud/config/get index 25ac2ca76..ec0721fca 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -71,9 +71,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. diff --git a/gcloud/config/help b/gcloud/config/help index a826dad85..dc90b281e 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -103,9 +103,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. diff --git a/gcloud/config/list b/gcloud/config/list index 0d7e8bd21..c1cc4562e 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -108,9 +108,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. diff --git a/gcloud/config/set b/gcloud/config/set index e4eb8a1e9..58b307237 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -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. diff --git a/gcloud/config/unset b/gcloud/config/unset index 7699b0f8a..635ab6e80 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -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. diff --git a/gcloud/container/fleet/memberships/generate-gateway-rbac b/gcloud/container/fleet/memberships/generate-gateway-rbac new file mode 100644 index 000000000..7685fc657 --- /dev/null +++ b/gcloud/container/fleet/memberships/generate-gateway-rbac @@ -0,0 +1,118 @@ +NAME + gcloud container fleet memberships generate-gateway-rbac - generate RBAC + policy files for connected clusters by the user + +SYNOPSIS + gcloud container fleet memberships generate-gateway-rbac [--anthos-support] + [--apply] [--context=CONTEXT] [--kubeconfig=KUBECONFIG] + [--membership=MEMBERSHIP] [--rbac-output-file=RBAC_OUTPUT_FILE] + [--revoke] [--role=ROLE] [--users=USERS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud container fleet memberships generate-gateway-rbac generates RBAC + policies to be used by Connect Gateway API. + + Upon success, this command will write the output RBAC policy to the + designated local file in dry run mode. + + Override RBAC policy: Y to override previous RBAC policy, N to stop. If + overriding the --role, Y will clean up the previous RBAC policy and then + apply the new one. + +EXAMPLES + The current implementation supports multiple modes: + + Dry run mode to generate the RBAC policy file, and write to local + directory: + + $ gcloud container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml + + Dry run mode to generate the RBAC policy, and print on screen: + + $ gcloud container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin + + Anthos support mode, generate the RBAC policy file with read-only + permission for TSE/Eng to debug customers' clusters: + + $ gcloud container fleet memberships generate-gateway-rbac \ + --membership=my-cluster --anthos-support + + Apply mode, generate the RBAC policy and apply it to the specified cluster: + + $ gcloud container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply + + Revoke mode, revoke the RBAC policy for the specified users: + + $ gcloud container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --revoke + +FLAGS + --anthos-support + If specified, this command will generate RBAC policy file for anthos + support. + + --apply + If specified, this command will generate RBAC policy and apply to the + specified cluster. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can get + this value from the command line by running command: kubectl config + current-context. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults to + $KUBECONFIG if it is set in the environment, otherwise defaults to + $HOME/.kube/config. + + --membership=MEMBERSHIP + Membership name to assign RBAC policy with. + + --rbac-output-file=RBAC_OUTPUT_FILE + If specified, this command will execute in dry run mode and write to + the file specified with this flag: the generated RBAC policy will not + be applied to Kubernetes clusters,instead it will be written to the + designated local file. + + --revoke + If specified, this command will revoke the RBAC policy for the + specified users. + + --role=ROLE + Namespace scoped role or cluster role. + + --users=USERS + User's email address or service account email address. + +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 + These variants are also available: + + $ gcloud alpha container fleet memberships generate-gateway-rbac + + $ gcloud beta container fleet memberships generate-gateway-rbac + diff --git a/gcloud/container/fleet/memberships/help b/gcloud/container/fleet/memberships/help index 267f04d1f..a8e6043b2 100644 --- a/gcloud/container/fleet/memberships/help +++ b/gcloud/container/fleet/memberships/help @@ -23,6 +23,9 @@ COMMANDS describe Describe a membership. + generate-gateway-rbac + Generate RBAC policy files for connected clusters by the user. + get-credentials Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register index 02e6e3be4..f2445ebc4 100644 --- a/gcloud/container/fleet/memberships/register +++ b/gcloud/container/fleet/memberships/register @@ -174,9 +174,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 diff --git a/gcloud/container/hub/memberships/generate-gateway-rbac b/gcloud/container/hub/memberships/generate-gateway-rbac new file mode 100644 index 000000000..f3f1a8019 --- /dev/null +++ b/gcloud/container/hub/memberships/generate-gateway-rbac @@ -0,0 +1,118 @@ +NAME + gcloud container hub memberships generate-gateway-rbac - generate RBAC + policy files for connected clusters by the user + +SYNOPSIS + gcloud container hub memberships generate-gateway-rbac [--anthos-support] + [--apply] [--context=CONTEXT] [--kubeconfig=KUBECONFIG] + [--membership=MEMBERSHIP] [--rbac-output-file=RBAC_OUTPUT_FILE] + [--revoke] [--role=ROLE] [--users=USERS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud container hub memberships generate-gateway-rbac generates RBAC + policies to be used by Connect Gateway API. + + Upon success, this command will write the output RBAC policy to the + designated local file in dry run mode. + + Override RBAC policy: Y to override previous RBAC policy, N to stop. If + overriding the --role, Y will clean up the previous RBAC policy and then + apply the new one. + +EXAMPLES + The current implementation supports multiple modes: + + Dry run mode to generate the RBAC policy file, and write to local + directory: + + $ gcloud container hub memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml + + Dry run mode to generate the RBAC policy, and print on screen: + + $ gcloud container hub memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin + + Anthos support mode, generate the RBAC policy file with read-only + permission for TSE/Eng to debug customers' clusters: + + $ gcloud container hub memberships generate-gateway-rbac \ + --membership=my-cluster --anthos-support + + Apply mode, generate the RBAC policy and apply it to the specified cluster: + + $ gcloud container hub memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply + + Revoke mode, revoke the RBAC policy for the specified users: + + $ gcloud container hub memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --revoke + +FLAGS + --anthos-support + If specified, this command will generate RBAC policy file for anthos + support. + + --apply + If specified, this command will generate RBAC policy and apply to the + specified cluster. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can get + this value from the command line by running command: kubectl config + current-context. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults to + $KUBECONFIG if it is set in the environment, otherwise defaults to + $HOME/.kube/config. + + --membership=MEMBERSHIP + Membership name to assign RBAC policy with. + + --rbac-output-file=RBAC_OUTPUT_FILE + If specified, this command will execute in dry run mode and write to + the file specified with this flag: the generated RBAC policy will not + be applied to Kubernetes clusters,instead it will be written to the + designated local file. + + --revoke + If specified, this command will revoke the RBAC policy for the + specified users. + + --role=ROLE + Namespace scoped role or cluster role. + + --users=USERS + User's email address or service account email address. + +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 + These variants are also available: + + $ gcloud alpha container hub memberships generate-gateway-rbac + + $ gcloud beta container hub memberships generate-gateway-rbac + diff --git a/gcloud/container/hub/memberships/help b/gcloud/container/hub/memberships/help index 9b4624e9c..ba86fdb59 100644 --- a/gcloud/container/hub/memberships/help +++ b/gcloud/container/hub/memberships/help @@ -23,6 +23,9 @@ COMMANDS describe Describe a membership. + generate-gateway-rbac + Generate RBAC policy files for connected clusters by the user. + get-credentials Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index 37d8ef002..63561af8e 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -173,9 +173,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 diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index 447409785..3bcc07711 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -8,8 +8,7 @@ SYNOPSIS | --backfill-all --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS) (--destination=DESTINATION - (--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - | --gcs-destination-config=GCS_DESTINATION_CONFIG)) + --gcs-destination-config=GCS_DESTINATION_CONFIG) (--source=SOURCE (--mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG)) [--labels=[KEY=VALUE,...]] [--force | --validate-only] @@ -115,37 +114,21 @@ REQUIRED FLAGS connection_profile. To set the connection_profile attribute: ▫ provide the argument --destination on the command line. - Exactly one of these must be specified: + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. - --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for - Google BigQuery Destination Config. + The JSON file is formatted as follows: - The JSON file is formatted as follows: + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } - { - "source_hierarchy_datasets": { - "dataset_template": { - "location": "us-central1", - "dataset_id_prefix": "my_prefix", - "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" - } - }, - "data_freshness": 3600 - } - - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for - Google Cloud Storage Destination Config. - - The JSON file is formatted as follows: - - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + This flag must be specified if any of the other arguments in this + group are specified. This must be specified. diff --git a/gcloud/datastream/streams/update b/gcloud/datastream/streams/update index 5c6d9e559..344306b8f 100644 --- a/gcloud/datastream/streams/update +++ b/gcloud/datastream/streams/update @@ -10,8 +10,7 @@ SYNOPSIS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS] [--clear-labels | --remove-labels=[KEY,...]] [--destination=DESTINATION - : --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - | --gcs-destination-config=GCS_DESTINATION_CONFIG] + : --gcs-destination-config=GCS_DESTINATION_CONFIG] [--force | --validate-only] [--source=SOURCE : --mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG] [GCLOUD_WIDE_FLAG ...] @@ -141,37 +140,18 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --destination on the command line. - At most one of these can be specified: + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. - --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - BigQuery Destination Config. + The JSON file is formatted as follows: - The JSON file is formatted as follows: - - { - "source_hierarchy_datasets": { - "dataset_template": { - "location": "us-central1", - "dataset_id_prefix": "my_prefix", - "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" - } - }, - "data_freshness": 3600 - } - - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. - - The JSON file is formatted as follows: - - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } At most one of these can be specified: diff --git a/gcloud/deploy/releases/create b/gcloud/deploy/releases/create index c22521a05..ed8c21bad 100644 --- a/gcloud/deploy/releases/create +++ b/gcloud/deploy/releases/create @@ -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 @@ -117,34 +118,9 @@ FLAGS $ gcloud 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 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 @@ -175,6 +151,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 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, diff --git a/gcloud/dns/dns-keys/list b/gcloud/dns/dns-keys/list index 3508d466a..cac238b8b 100644 --- a/gcloud/dns/dns-keys/list +++ b/gcloud/dns/dns-keys/list @@ -15,8 +15,8 @@ EXAMPLES To see the DS records for every key-signing DnsKey in a managed zone, run: - $ gcloud dns dns-keys list --zone=my_zone 3 \ - --format='value(ds_record())' --filter='type=keySigning' + $ gcloud dns dns-keys list --zone=my_zone \ + --filter='type=keySigning' --format='value(ds_record())' REQUIRED FLAGS --zone=ZONE diff --git a/gcloud/domains/registrations/help b/gcloud/domains/registrations/help index d5b35e97b..68b100def 100644 --- a/gcloud/domains/registrations/help +++ b/gcloud/domains/registrations/help @@ -43,9 +43,15 @@ COMMANDS get-transfer-parameters Get transfer parameters of a specific domain. + import + Import a domain from Google Domains registrar to Cloud Domains. + list List Cloud Domains registrations. + list-importable-domains + List Google Domains registrations importable into Cloud Domains. + register Register a new domain. diff --git a/gcloud/domains/registrations/import b/gcloud/domains/registrations/import new file mode 100644 index 000000000..4d7b369b6 --- /dev/null +++ b/gcloud/domains/registrations/import @@ -0,0 +1,73 @@ +NAME + gcloud domains registrations import - import a domain from Google Domains + registrar to Cloud Domains + +SYNOPSIS + gcloud domains registrations import REGISTRATION [--async] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + 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 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 + These variants are also available: + + $ gcloud alpha domains registrations import + + $ gcloud beta domains registrations import + diff --git a/gcloud/domains/registrations/list-importable-domains b/gcloud/domains/registrations/list-importable-domains new file mode 100644 index 000000000..fcc07b451 --- /dev/null +++ b/gcloud/domains/registrations/list-importable-domains @@ -0,0 +1,68 @@ +NAME + gcloud domains registrations list-importable-domains - list Google Domains + registrations importable into Cloud Domains + +SYNOPSIS + gcloud domains registrations list-importable-domains [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + 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 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 + These variants are also available: + + $ gcloud alpha domains registrations list-importable-domains + + $ gcloud beta domains registrations list-importable-domains + diff --git a/gcloud/functions/add-iam-policy-binding b/gcloud/functions/add-iam-policy-binding index 7d2b45446..0ef4fcd8a 100644 --- a/gcloud/functions/add-iam-policy-binding +++ b/gcloud/functions/add-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions add-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Adds an IAM policy binding for a Google Cloud Function. @@ -66,6 +66,13 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/add-invoker-policy-binding b/gcloud/functions/add-invoker-policy-binding new file mode 100644 index 000000000..5a64dcc50 --- /dev/null +++ b/gcloud/functions/add-invoker-policy-binding @@ -0,0 +1,77 @@ +NAME + gcloud functions add-invoker-policy-binding - adds an invoker binding to + the IAM policy of a Google Cloud Function + +SYNOPSIS + gcloud functions add-invoker-policy-binding (NAME : --region=REGION) + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command applies to Cloud Functions V2 only. + +EXAMPLES + To add the invoker policy binding for FUNCTION-1 from role ROLE-1 for + member MEMBER-1 run: + + $ gcloud functions add-invoker-policy-binding FUNCTION-1 \ + --member=MEMBER-1 + +POSITIONAL ARGUMENTS + Function resource - The Cloud function name to add the invoker binding to. + 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 NAME on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + NAME + ID of the function or fully qualified identifier for the function. To + set the function attribute: + ▸ provide the argument NAME on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Cloud region for the function. Overrides the default + functions/region property value for this command invocation. To set + the region attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property functions/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add to the IAM policy. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + +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 + These variants are also available: + + $ gcloud alpha functions add-invoker-policy-binding + + $ gcloud beta functions add-invoker-policy-binding + diff --git a/gcloud/functions/call b/gcloud/functions/call index 11dc5afb0..a9281f19b 100644 --- a/gcloud/functions/call +++ b/gcloud/functions/call @@ -2,8 +2,8 @@ NAME gcloud functions call - triggers execution of a Google Cloud Function SYNOPSIS - gcloud functions call (NAME : --region=REGION) [--data=DATA] - [GCLOUD_WIDE_FLAG ...] + gcloud functions call (NAME : --region=REGION) [--gen2] + [--cloud-event=CLOUD_EVENT | --data=DATA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Triggers execution of a Google Cloud Function. @@ -52,8 +52,26 @@ POSITIONAL ARGUMENTS ▸ set the property functions/region. FLAGS - --data=DATA - JSON string with data that will be passed to the function. + --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. + + At most one of these can be specified: + + --cloud-event=CLOUD_EVENT + JSON encoded string with a CloudEvent in structured content mode. + + Mutually exclusive with --data flag. + + Use for Cloud Functions 2nd Gen CloudEvent functions. The CloudEvent + object will be sent to your function as a binary content mode message + with the top-level 'data' field set as the HTTP body and all other + JSON fields sent as HTTP headers. + + --data=DATA + JSON string with data that will be passed to the function. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/functions/delete b/gcloud/functions/delete index 92042a9cd..f53f42a41 100644 --- a/gcloud/functions/delete +++ b/gcloud/functions/delete @@ -2,7 +2,8 @@ NAME gcloud functions delete - delete a Google Cloud Function SYNOPSIS - gcloud functions delete (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] + gcloud functions delete (NAME : --region=REGION) [--gen2] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a Google Cloud Function. @@ -36,6 +37,13 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. +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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 4ef5c6d75..d34e38de9 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -4,12 +4,15 @@ NAME SYNOPSIS gcloud functions deploy (NAME : --region=REGION) [--allow-unauthenticated] [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS] - [--entry-point=ENTRY_POINT] [--ignore-file=IGNORE_FILE] + [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--memory=MEMORY] [--retry] - [--runtime=RUNTIME] + [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] [--security-level=SECURITY_LEVEL; default="secure-always"] + [--serve-all-traffic-latest-revision] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] [--stage-bucket=STAGE_BUCKET] [--timeout=TIMEOUT] + [--trigger-location=TRIGGER_LOCATION] + [--trigger-service-account=TRIGGER_SERVICE_ACCOUNT] [--update-labels=[KEY=VALUE,...]] [--build-env-vars-file=FILE_PATH | --clear-build-env-vars | --set-build-env-vars=[KEY=VALUE,...] @@ -36,7 +39,9 @@ SYNOPSIS [--clear-vpc-connector | --vpc-connector=VPC_CONNECTOR] [--trigger-bucket=TRIGGER_BUCKET | --trigger-http | --trigger-topic=TRIGGER_TOPIC - | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE] + | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE + | --trigger-event-filters=[ATTRIBUTE=VALUE,...] + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -112,6 +117,12 @@ FLAGS this is name of a function exported by the module specified in source_location. + --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. + --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. @@ -131,6 +142,17 @@ FLAGS --retry If specified, then the function will be retried in case of a failure. + --run-service-account=RUN_SERVICE_ACCOUNT + The email address of the IAM service account associated with the Cloud + Run service for the function. The service account represents the + identity of the running function, and determines what permissions the + function has. + + If not provided, the function will use the project's default service + account for Compute Engine. + + This is only relevant when --gen2 is provided. + --runtime=RUNTIME Runtime in which to run the function. @@ -167,6 +189,10 @@ FLAGS only HTTPS is supported. SECURITY_LEVEL must be one of: secure-always, secure-optional. + --serve-all-traffic-latest-revision + If specified, latest function revision will be served all traffic. This + is only relevant when --gen2 is provided. + --service-account=SERVICE_ACCOUNT The email address of the IAM service account associated with the function at runtime. The service account represents the identity of the @@ -256,6 +282,21 @@ FLAGS Cannot be more than 540s. See $ gcloud topic datetimes for information on duration formats. + --trigger-location=TRIGGER_LOCATION + The location of the trigger, which must be a region or multi-region + where the relevant events originate. This is only relevant when --gen2 + is provided. + + --trigger-service-account=TRIGGER_SERVICE_ACCOUNT + The email address of the IAM service account associated with the + Eventarc trigger for the function. This is used for authenticated + invocation. + + If not provided, the function will use the project's default service + account for Compute Engine. + + This is only relevant when --gen2 is provided. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -498,8 +539,8 @@ FLAGS If you don't specify a trigger when deploying an update to an existing function it will keep its current trigger. You must specify - --trigger-topic, --trigger-bucket, --trigger-http or (--trigger-event AND - --trigger-resource) when deploying a new function. + --trigger-topic, --trigger-bucket, --trigger-http, --trigger-event-filters + or (--trigger-event AND --trigger-resource) when deploying a new function. At most one of these can be specified: @@ -532,6 +573,17 @@ FLAGS must be a bucket name. For a list of expected resources, call gcloud functions event-types list. + --trigger-event-filters=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger. The criteria can be + specified either as a single comma-separated argument or as multiple + arguments. This is only relevant when --gen2 is provided. + + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger in path pattern + format. The criteria can be specified as a single comma-separated + argument or as multiple arguments. This is only relevant when --gen2 + is provided. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/describe b/gcloud/functions/describe index db55a2cda..fcc6a6303 100644 --- a/gcloud/functions/describe +++ b/gcloud/functions/describe @@ -2,7 +2,8 @@ NAME gcloud functions describe - display details of a Google Cloud Function SYNOPSIS - gcloud functions describe (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] + gcloud functions describe (NAME : --region=REGION) [--gen2] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Display details of a Google Cloud Function. @@ -36,6 +37,13 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. +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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/event-types/list b/gcloud/functions/event-types/list index fd0147479..5fbb0b189 100644 --- a/gcloud/functions/event-types/list +++ b/gcloud/functions/event-types/list @@ -3,7 +3,7 @@ NAME trigger for a Google Cloud Function SYNOPSIS - gcloud functions event-types list [GCLOUD_WIDE_FLAG ...] + gcloud functions event-types list [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud functions event-types list displays types of events that can be a @@ -16,6 +16,13 @@ DESCRIPTION corresponding default value (in which case the --trigger-resource flag may be omitted). +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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/get-iam-policy b/gcloud/functions/get-iam-policy index bc591f7bc..50f2e2af4 100644 --- a/gcloud/functions/get-iam-policy +++ b/gcloud/functions/get-iam-policy @@ -3,7 +3,7 @@ NAME Function SYNOPSIS - gcloud functions get-iam-policy (NAME : --region=REGION) + gcloud functions get-iam-policy (NAME : --region=REGION) [--gen2] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +44,13 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. +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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/functions/help b/gcloud/functions/help index ce4661a8c..7e2d65a22 100644 --- a/gcloud/functions/help +++ b/gcloud/functions/help @@ -33,6 +33,9 @@ COMMANDS add-iam-policy-binding Adds an IAM policy binding for a Google Cloud Function. + add-invoker-policy-binding + Adds an invoker binding to the IAM policy of a Google Cloud Function. + call Triggers execution of a Google Cloud Function. @@ -54,6 +57,10 @@ COMMANDS remove-iam-policy-binding Removes an IAM policy binding from a Google Cloud Function. + remove-invoker-policy-binding + Removes an invoker binding from the IAM policy of a Google Cloud + Function. + set-iam-policy Sets IAM policy for a Google Cloud Function. diff --git a/gcloud/functions/logs/read b/gcloud/functions/logs/read index dd15f0894..4e340ab22 100644 --- a/gcloud/functions/logs/read +++ b/gcloud/functions/logs/read @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions logs read [NAME] [--end-time=END_TIME] - [--execution-id=EXECUTION_ID] [--limit=LIMIT; default=20] + [--execution-id=EXECUTION_ID] [--gen2] [--limit=LIMIT; default=20] [--min-log-level=MIN_LOG_LEVEL] [--region=REGION] [--start-time=START_TIME] [--filter=EXPRESSION] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -28,6 +28,12 @@ FLAGS --execution-id=EXECUTION_ID Execution ID for which logs are to be displayed. + --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. + --limit=LIMIT; default=20 Number of log entries to be fetched; must not be greater than 1000. Note that the most recent entries in the specified time range are diff --git a/gcloud/functions/regions/list b/gcloud/functions/regions/list index 2d365cbe2..40950e89b 100644 --- a/gcloud/functions/regions/list +++ b/gcloud/functions/regions/list @@ -3,13 +3,20 @@ NAME Functions SYNOPSIS - gcloud functions regions list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud functions regions list [--gen2] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List regions available to 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/functions/remove-iam-policy-binding b/gcloud/functions/remove-iam-policy-binding index e0e2fd24e..30553531c 100644 --- a/gcloud/functions/remove-iam-policy-binding +++ b/gcloud/functions/remove-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions remove-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Removes an IAM policy binding from a Google Cloud Function. @@ -67,6 +67,13 @@ REQUIRED FLAGS --role=ROLE The role to remove the principal from. +OPTIONAL 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/functions/remove-invoker-policy-binding b/gcloud/functions/remove-invoker-policy-binding new file mode 100644 index 000000000..6d81fbf63 --- /dev/null +++ b/gcloud/functions/remove-invoker-policy-binding @@ -0,0 +1,81 @@ +NAME + gcloud functions remove-invoker-policy-binding - removes an invoker binding + from the IAM policy of a Google Cloud Function + +SYNOPSIS + gcloud functions remove-invoker-policy-binding (NAME : --region=REGION) + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command applies to Cloud Functions V2 only. + +EXAMPLES + To remove the invoker policy binding for FUNCTION-1 from role ROLE-1 for + member MEMBER-1 run: + + $ gcloud functions remove-invoker-policy-binding FUNCTION-1 \ + --member=MEMBER-1 + +POSITIONAL ARGUMENTS + Function resource - The Cloud function name to remove the invoker binding + from. 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 NAME on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + NAME + ID of the function or fully qualified identifier for the function. To + set the function attribute: + ▸ provide the argument NAME on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Cloud region for the function. Overrides the default + functions/region property value for this command invocation. To set + the region attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property functions/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove from the IAM policy. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + +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 + These variants are also available: + + $ gcloud alpha functions remove-invoker-policy-binding + + $ gcloud beta functions remove-invoker-policy-binding + diff --git a/gcloud/functions/set-iam-policy b/gcloud/functions/set-iam-policy index 9bc950ba2..b3e45439b 100644 --- a/gcloud/functions/set-iam-policy +++ b/gcloud/functions/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions set-iam-policy (NAME : --region=REGION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] + [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Sets IAM policy for a Google Cloud Function. @@ -47,6 +47,13 @@ POSITIONAL ARGUMENTS POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. +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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/healthcare/fhir-stores/export/bq b/gcloud/healthcare/fhir-stores/export/bq index 6b292a966..502037ea2 100644 --- a/gcloud/healthcare/fhir-stores/export/bq +++ b/gcloud/healthcare/fhir-stores/export/bq @@ -65,13 +65,17 @@ REQUIRED FLAGS BigQuery dataset that houses the BigQuery tables. --schema-type=SCHEMA_TYPE - Specifies the output schema type. SCHEMA_TYPE must be (currently only - one value is supported): + Specifies the output schema type. SCHEMA_TYPE must be one of: analytics Analytics schema defined by the FHIR community. See https://github.com/rbrush/sql-on-fhir/blob/master/sql-on-fhir.md. + analytics_v2 + Analytics V2, similar to Analytics schema type, with added support + for extensions with one or more occurrences and contained resources + to be represented in stringified JSON. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 72f87ce11..9eabd90f2 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -22,7 +22,7 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--image=IMAGE | --source=SOURCE] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION - --clear-vpc-connector --[no-]cpu-throttling + --clear-vpc-connector --[no-]cpu-throttling --description=DESCRIPTION --revision-suffix=REVISION_SUFFIX --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -376,6 +376,9 @@ FLAGS serving requests. Use --cpu-throttling to enable and --no-cpu-throttling to disable. + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + --revision-suffix=REVISION_SUFFIX Specify the suffix of the revision name. Revision names always start with the service name automatically. For example, specifying