From 3b84182be4600d98ff939fe0d7e801b24e826efb Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 15 May 2024 09:19:06 +0000 Subject: [PATCH] gcloud: Wed May 15 09:19:06 UTC 2024 --- gcloud/_version | 10 +- gcloud/alloydb/instances/create | 2 +- gcloud/alloydb/instances/create-secondary | 29 +- gcloud/alloydb/instances/update | 2 +- .../cloud-bindings/create | 70 ++++- .../cloud-bindings/help | 2 +- .../cloud-bindings/list | 16 +- .../cloud-bindings/update | 33 +- gcloud/alpha/alloydb/instances/create | 2 +- .../alpha/alloydb/instances/create-secondary | 29 +- gcloud/alpha/alloydb/instances/update | 2 +- gcloud/alpha/compute/firewall-rules/migrate | 24 +- .../alpha/compute/instance-templates/create | 30 +- .../instance-templates/create-with-container | 68 +++- gcloud/alpha/compute/instances/create | 35 ++- .../compute/instances/create-with-container | 71 ++++- gcloud/alpha/compute/instances/help | 4 +- gcloud/alpha/compute/instances/move | 12 +- .../delegated-sub-prefixes/create | 10 +- gcloud/alpha/compute/routers/add-bgp-peer | 14 +- gcloud/alpha/compute/routers/add-route-policy | 66 ++++ .../compute/routers/download-route-policy | 65 ++++ gcloud/alpha/compute/routers/get-route-policy | 57 ++++ gcloud/alpha/compute/routers/help | 22 ++ gcloud/alpha/compute/routers/list-bgp-routes | 120 +++++++ .../alpha/compute/routers/list-route-policies | 86 +++++ .../alpha/compute/routers/remove-route-policy | 57 ++++ gcloud/alpha/compute/routers/update-bgp-peer | 14 +- .../alpha/compute/routers/upload-route-policy | 65 ++++ .../node-groups/perform-maintenance | 4 +- .../container/fleet/mesh/debug/proxy-config | 5 +- .../container/hub/mesh/debug/proxy-config | 5 +- gcloud/alpha/dataplex/entries/create | 293 +++++++++++++++++ gcloud/alpha/dataplex/entries/delete | 77 +++++ gcloud/alpha/dataplex/entries/describe | 127 ++++++++ gcloud/alpha/dataplex/entries/help | 49 +++ gcloud/alpha/dataplex/entries/list | 103 ++++++ gcloud/alpha/dataplex/entries/lookup | 131 ++++++++ gcloud/alpha/dataplex/entries/remove-aspects | 113 +++++++ gcloud/alpha/dataplex/entries/update | 295 ++++++++++++++++++ gcloud/alpha/dataplex/entries/update-aspects | 130 ++++++++ gcloud/alpha/dataplex/help | 3 + .../developer-connect/connections/create | 190 +++++++++++ .../developer-connect/connections/delete | 94 ++++++ .../developer-connect/connections/describe | 65 ++++ .../connections/git-repository-links/create | 136 ++++++++ .../connections/git-repository-links/delete | 105 +++++++ .../connections/git-repository-links/describe | 76 +++++ .../connections/git-repository-links/help | 37 +++ .../connections/git-repository-links/list | 101 ++++++ .../alpha/developer-connect/connections/help | 45 +++ .../alpha/developer-connect/connections/list | 86 +++++ .../developer-connect/connections/update | 250 +++++++++++++++ gcloud/alpha/developer-connect/help | 29 ++ .../alpha/developer-connect/operations/cancel | 65 ++++ .../alpha/developer-connect/operations/delete | 65 ++++ .../developer-connect/operations/describe | 65 ++++ .../alpha/developer-connect/operations/help | 38 +++ .../alpha/developer-connect/operations/list | 86 +++++ .../alpha/developer-connect/operations/wait | 65 ++++ gcloud/alpha/functions/deploy | 6 + gcloud/alpha/functions/help | 3 - gcloud/alpha/functions/upgrade | 105 ------- gcloud/alpha/kms/keys/create | 26 +- gcloud/alpha/kms/keys/update | 26 +- gcloud/alpha/kms/keys/versions/import | 2 +- gcloud/alpha/logging/views/describe | 2 +- gcloud/alpha/netapp/storage-pools/create | 15 +- gcloud/alpha/netapp/storage-pools/help | 3 + gcloud/alpha/netapp/storage-pools/switch | 78 +++++ gcloud/alpha/netapp/storage-pools/update | 19 +- gcloud/alpha/netapp/volumes/create | 13 + gcloud/alpha/netapp/volumes/update | 13 + gcloud/alpha/number-registry/help | 29 ++ .../alpha/number-registry/operations/cancel | 64 ++++ .../alpha/number-registry/operations/delete | 64 ++++ .../alpha/number-registry/operations/describe | 64 ++++ gcloud/alpha/number-registry/operations/help | 38 +++ gcloud/alpha/number-registry/operations/list | 85 +++++ gcloud/alpha/number-registry/operations/wait | 64 ++++ .../number-registry/registry-books/create | 96 ++++++ .../number-registry/registry-books/delete | 88 ++++++ .../number-registry/registry-books/describe | 68 ++++ .../alpha/number-registry/registry-books/help | 52 +++ .../registry-books/historical-events/help | 28 ++ .../registry-books/historical-events/show | 95 ++++++ .../alpha/number-registry/registry-books/list | 86 +++++ .../registry-books/node-events/help | 28 ++ .../registry-books/node-events/show | 101 ++++++ .../registry-books/registry-nodes/create | 155 +++++++++ .../registry-books/registry-nodes/delete | 97 ++++++ .../registry-books/registry-nodes/describe | 77 +++++ .../registry-books/registry-nodes/help | 43 +++ .../registry-books/registry-nodes/list | 102 ++++++ .../registry-books/registry-nodes/search | 118 +++++++ .../registry-books/registry-nodes/update | 245 +++++++++++++++ .../number-registry/registry-books/update | 135 ++++++++ gcloud/alpha/scc/findings/group | 61 ++-- gcloud/alpha/scc/findings/list | 55 ++-- gcloud/alpha/scc/findings/list-marks | 11 +- gcloud/alpha/scc/manage/help | 3 + gcloud/alpha/scc/manage/services/describe | 74 +++++ gcloud/alpha/scc/manage/services/help | 35 +++ gcloud/alpha/scc/manage/services/list | 92 ++++++ gcloud/alpha/scc/manage/services/update | 91 ++++++ gcloud/app/deploy | 11 +- gcloud/beta/alloydb/instances/create | 2 +- .../beta/alloydb/instances/create-secondary | 29 +- gcloud/beta/alloydb/instances/update | 2 +- gcloud/beta/app/deploy | 13 +- gcloud/beta/compute/firewall-rules/migrate | 24 +- gcloud/beta/compute/instance-templates/create | 30 +- .../instance-templates/create-with-container | 86 ++++- gcloud/beta/compute/instances/create | 33 +- .../compute/instances/create-with-container | 86 ++++- gcloud/beta/compute/instances/help | 4 +- gcloud/beta/compute/instances/move | 12 +- .../compute/public-delegated-prefixes/create | 10 +- .../delegated-sub-prefixes/create | 10 +- gcloud/beta/compute/routers/add-bgp-peer | 14 +- gcloud/beta/compute/routers/add-route-policy | 63 ++++ .../compute/routers/download-route-policy | 63 ++++ gcloud/beta/compute/routers/get-route-policy | 55 ++++ gcloud/beta/compute/routers/help | 22 ++ gcloud/beta/compute/routers/list-bgp-routes | 118 +++++++ .../beta/compute/routers/list-route-policies | 84 +++++ .../beta/compute/routers/remove-route-policy | 55 ++++ gcloud/beta/compute/routers/update-bgp-peer | 14 +- .../beta/compute/routers/upload-route-policy | 63 ++++ .../node-groups/perform-maintenance | 6 +- .../container/fleet/mesh/debug/proxy-config | 5 +- .../container/hub/mesh/debug/proxy-config | 5 +- gcloud/beta/functions/deploy | 6 + gcloud/beta/kms/keys/create | 26 +- gcloud/beta/kms/keys/update | 26 +- gcloud/beta/kms/keys/versions/import | 2 +- gcloud/beta/logging/views/describe | 2 +- gcloud/beta/netapp/storage-pools/create | 15 +- gcloud/beta/netapp/storage-pools/help | 3 + gcloud/beta/netapp/storage-pools/switch | 75 +++++ gcloud/beta/netapp/storage-pools/update | 19 +- gcloud/beta/netapp/volumes/create | 13 + gcloud/beta/netapp/volumes/update | 13 + gcloud/beta/scc/findings/group | 61 ++-- gcloud/beta/scc/findings/list | 55 ++-- gcloud/beta/scc/findings/list-marks | 11 +- gcloud/compute/instance-templates/create | 30 +- .../instance-templates/create-with-container | 77 ++++- gcloud/compute/instances/create | 33 +- .../compute/instances/create-with-container | 77 ++++- gcloud/compute/instances/help | 3 +- gcloud/compute/instances/move | 4 + .../compute/public-delegated-prefixes/create | 10 +- .../delegated-sub-prefixes/create | 14 +- gcloud/compute/routers/add-bgp-peer | 42 ++- gcloud/compute/routers/add-interface | 24 +- gcloud/compute/routers/create | 8 + gcloud/compute/routers/update | 10 +- gcloud/compute/routers/update-bgp-peer | 49 ++- gcloud/compute/routers/update-interface | 20 +- .../compute/sole-tenancy/node-groups/create | 18 +- gcloud/compute/sole-tenancy/node-groups/help | 3 + .../node-groups/perform-maintenance | 68 ++++ gcloud/dataplex/entries/create | 290 +++++++++++++++++ gcloud/dataplex/entries/delete | 73 +++++ gcloud/dataplex/entries/describe | 124 ++++++++ gcloud/dataplex/entries/help | 46 +++ gcloud/dataplex/entries/list | 100 ++++++ gcloud/dataplex/entries/lookup | 127 ++++++++ gcloud/dataplex/entries/remove-aspects | 110 +++++++ gcloud/dataplex/entries/update | 288 +++++++++++++++++ gcloud/dataplex/entries/update-aspects | 127 ++++++++ gcloud/dataplex/help | 3 + gcloud/functions/deploy | 6 + gcloud/infra-manager/deployments/apply | 26 ++ gcloud/infra-manager/previews/create | 26 +- gcloud/kms/keys/create | 26 +- gcloud/kms/keys/update | 26 +- gcloud/kms/keys/versions/import | 2 +- gcloud/logging/views/add-iam-policy-binding | 135 ++++++++ gcloud/logging/views/describe | 2 +- gcloud/logging/views/get-iam-policy | 63 ++++ gcloud/logging/views/help | 12 + .../logging/views/remove-iam-policy-binding | 141 +++++++++ gcloud/logging/views/set-iam-policy | 71 +++++ gcloud/scc/findings/group | 61 ++-- gcloud/scc/findings/list | 55 ++-- gcloud/scc/findings/list-marks | 11 +- gcloud/scc/manage/help | 3 + gcloud/scc/manage/services/describe | 69 ++++ gcloud/scc/manage/services/help | 32 ++ gcloud/scc/manage/services/list | 88 ++++++ gcloud/scc/manage/services/update | 88 ++++++ 193 files changed, 10091 insertions(+), 581 deletions(-) create mode 100644 gcloud/alpha/compute/routers/add-route-policy create mode 100644 gcloud/alpha/compute/routers/download-route-policy create mode 100644 gcloud/alpha/compute/routers/get-route-policy create mode 100644 gcloud/alpha/compute/routers/list-bgp-routes create mode 100644 gcloud/alpha/compute/routers/list-route-policies create mode 100644 gcloud/alpha/compute/routers/remove-route-policy create mode 100644 gcloud/alpha/compute/routers/upload-route-policy create mode 100644 gcloud/alpha/dataplex/entries/create create mode 100644 gcloud/alpha/dataplex/entries/delete create mode 100644 gcloud/alpha/dataplex/entries/describe create mode 100644 gcloud/alpha/dataplex/entries/help create mode 100644 gcloud/alpha/dataplex/entries/list create mode 100644 gcloud/alpha/dataplex/entries/lookup create mode 100644 gcloud/alpha/dataplex/entries/remove-aspects create mode 100644 gcloud/alpha/dataplex/entries/update create mode 100644 gcloud/alpha/dataplex/entries/update-aspects create mode 100644 gcloud/alpha/developer-connect/connections/create create mode 100644 gcloud/alpha/developer-connect/connections/delete create mode 100644 gcloud/alpha/developer-connect/connections/describe create mode 100644 gcloud/alpha/developer-connect/connections/git-repository-links/create create mode 100644 gcloud/alpha/developer-connect/connections/git-repository-links/delete create mode 100644 gcloud/alpha/developer-connect/connections/git-repository-links/describe create mode 100644 gcloud/alpha/developer-connect/connections/git-repository-links/help create mode 100644 gcloud/alpha/developer-connect/connections/git-repository-links/list create mode 100644 gcloud/alpha/developer-connect/connections/help create mode 100644 gcloud/alpha/developer-connect/connections/list create mode 100644 gcloud/alpha/developer-connect/connections/update create mode 100644 gcloud/alpha/developer-connect/help create mode 100644 gcloud/alpha/developer-connect/operations/cancel create mode 100644 gcloud/alpha/developer-connect/operations/delete create mode 100644 gcloud/alpha/developer-connect/operations/describe create mode 100644 gcloud/alpha/developer-connect/operations/help create mode 100644 gcloud/alpha/developer-connect/operations/list create mode 100644 gcloud/alpha/developer-connect/operations/wait delete mode 100644 gcloud/alpha/functions/upgrade create mode 100644 gcloud/alpha/netapp/storage-pools/switch create mode 100644 gcloud/alpha/number-registry/help create mode 100644 gcloud/alpha/number-registry/operations/cancel create mode 100644 gcloud/alpha/number-registry/operations/delete create mode 100644 gcloud/alpha/number-registry/operations/describe create mode 100644 gcloud/alpha/number-registry/operations/help create mode 100644 gcloud/alpha/number-registry/operations/list create mode 100644 gcloud/alpha/number-registry/operations/wait create mode 100644 gcloud/alpha/number-registry/registry-books/create create mode 100644 gcloud/alpha/number-registry/registry-books/delete create mode 100644 gcloud/alpha/number-registry/registry-books/describe create mode 100644 gcloud/alpha/number-registry/registry-books/help create mode 100644 gcloud/alpha/number-registry/registry-books/historical-events/help create mode 100644 gcloud/alpha/number-registry/registry-books/historical-events/show create mode 100644 gcloud/alpha/number-registry/registry-books/list create mode 100644 gcloud/alpha/number-registry/registry-books/node-events/help create mode 100644 gcloud/alpha/number-registry/registry-books/node-events/show create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/create create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/delete create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/describe create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/help create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/list create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/search create mode 100644 gcloud/alpha/number-registry/registry-books/registry-nodes/update create mode 100644 gcloud/alpha/number-registry/registry-books/update create mode 100644 gcloud/alpha/scc/manage/services/describe create mode 100644 gcloud/alpha/scc/manage/services/help create mode 100644 gcloud/alpha/scc/manage/services/list create mode 100644 gcloud/alpha/scc/manage/services/update create mode 100644 gcloud/beta/compute/routers/add-route-policy create mode 100644 gcloud/beta/compute/routers/download-route-policy create mode 100644 gcloud/beta/compute/routers/get-route-policy create mode 100644 gcloud/beta/compute/routers/list-bgp-routes create mode 100644 gcloud/beta/compute/routers/list-route-policies create mode 100644 gcloud/beta/compute/routers/remove-route-policy create mode 100644 gcloud/beta/compute/routers/upload-route-policy create mode 100644 gcloud/beta/netapp/storage-pools/switch create mode 100644 gcloud/compute/sole-tenancy/node-groups/perform-maintenance create mode 100644 gcloud/dataplex/entries/create create mode 100644 gcloud/dataplex/entries/delete create mode 100644 gcloud/dataplex/entries/describe create mode 100644 gcloud/dataplex/entries/help create mode 100644 gcloud/dataplex/entries/list create mode 100644 gcloud/dataplex/entries/lookup create mode 100644 gcloud/dataplex/entries/remove-aspects create mode 100644 gcloud/dataplex/entries/update create mode 100644 gcloud/dataplex/entries/update-aspects create mode 100644 gcloud/logging/views/add-iam-policy-binding create mode 100644 gcloud/logging/views/get-iam-policy create mode 100644 gcloud/logging/views/remove-iam-policy-binding create mode 100644 gcloud/logging/views/set-iam-policy create mode 100644 gcloud/scc/manage/services/describe create mode 100644 gcloud/scc/manage/services/help create mode 100644 gcloud/scc/manage/services/list create mode 100644 gcloud/scc/manage/services/update diff --git a/gcloud/_version b/gcloud/_version index 5b0dfbf25..6fccd4aad 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 475.0.0 -alpha 2024.05.03 -beta 2024.05.03 +Google Cloud SDK 476.0.0 +alpha 2024.05.10 +beta 2024.05.10 bq 2.1.4 bundled-python3-unix 3.11.8 -core 2024.05.03 +core 2024.05.10 gcloud-crc32c 1.0.0 -gsutil 5.27 +gsutil 5.29 diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 10e07bffd..74ae46fb3 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -128,7 +128,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/alloydb/instances/create-secondary b/gcloud/alloydb/instances/create-secondary index bde6c986d..8eabcf39f 100644 --- a/gcloud/alloydb/instances/create-secondary +++ b/gcloud/alloydb/instances/create-secondary @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alloydb instances create-secondary INSTANCE --cluster=CLUSTER - --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] + --region=REGION [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] + [--async] [--availability-type=AVAILABILITY_TYPE] + [--[no-]require-connectors] [--ssl-mode=SSL_MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,6 +31,16 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP + Specify to enable or disable public IP on an instance. On instance + creation only disabling public IP is allowed. If you want to enable + public IP, an instance must be created with public IP disabled first, + then update the instance to enable public IP. ASSIGN_INBOUND_PUBLIC_IP + must be (only one value is supported): + + NO_PUBLIC_IP + This disables public IP on the instance. + --async Return immediately, without waiting for the operation in progress to complete. @@ -45,6 +57,21 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --[no-]require-connectors + Enable or disable enforcing connectors only (ex: AuthProxy) connections + to the database. Use --require-connectors to enable and + --no-require-connectors to disable. + + --ssl-mode=SSL_MODE + Specify the SSL mode to use when the instance connects to the database. + Default SSL mode will match what is set on the primary instance. + SSL_MODE must be one of: + + ALLOW_UNENCRYPTED_AND_ENCRYPTED + SSL connections are optional. CA verification is not enforced. + ENCRYPTED_ONLY + SSL connections are required. CA verification is not enforced. + 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/alloydb/instances/update b/gcloud/alloydb/instances/update index a84b4e98d..79139029a 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -118,7 +118,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/create b/gcloud/alpha/access-context-manager/cloud-bindings/create index 9db2b6b2c..97d487b2a 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/create +++ b/gcloud/alpha/access-context-manager/cloud-bindings/create @@ -6,27 +6,58 @@ SYNOPSIS gcloud alpha access-context-manager cloud-bindings create --group-key=GROUP_KEY [--dry-run-level=[DRY_RUN_LEVEL,...]] [--level=[LEVEL,...]] [--organization=ORGANIZATION] - [GCLOUD_WIDE_FLAG ...] + [--restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS, + ...]] + [--restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES, + ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a new cloud access binding. The access level will be bound - with the group. The access level will be enforced when any user in the - group tries to access the Google cloud console or API. + (ALPHA) Create a new access binding. The access level will be bound with + the group and the restricted client application. The access level is + enforced at the organization level for all context-aware access group + members, as specified in the bind. If a restricted client application is + specified, then the enforcement applies only to the specified application, + and not to the entire organization. EXAMPLES - To create a new cloud access binding, run: + To create a new cloud access binding at the organization level, run: $ gcloud alpha access-context-manager cloud-bindings create \ --group-key=my-group-key \ --level=accessPolicies/123/accessLevels/abc - To create a new cloud access binding for the dry run access level, run: + To create a new cloud access binding for particular applications, run: + + $ gcloud alpha access-context-manager cloud-bindings create \ + --group-key=my-group-key \ + --level=accessPolicies/123/accessLevels/abc \ + --organization='1234567890' \ + --restricted-client-application-names='Google Cloud SDK, Cloud + Console' \ + --restricted-client-application-client-ids='123456789.apps.googl\ + eusercontent.com' + + To create a new cloud access binding for the dry run access level at the + organization level, run: $ gcloud alpha access-context-manager cloud-bindings create \ --group-key=my-group-key \ --level=accessPolicies/123/accessLevels/abc \ --dry-run-level=accessPolicies/123/accessLevels/def + To create a new cloud access binding for the dry run access level for + particular applications, run: + + $ gcloud alpha access-context-manager cloud-bindings create \ + --group-key=my-group-key \ + --level=accessPolicies/123/accessLevels/abc \ + --dry-run-level=accessPolicies/123/accessLevels/def \ + --organization='1234567890' \ + --restricted-client-application-names='Google Cloud SDK, Cloud + Console' \ + --restricted-client-application-client-ids='123456789.apps.googl\ + eusercontent.com' + REQUIRED FLAGS --group-key=GROUP_KEY Google Group id whose members are subject to the restrictions of this @@ -34,19 +65,32 @@ REQUIRED FLAGS OPTIONAL FLAGS --dry-run-level=[DRY_RUN_LEVEL,...] - The dry run access level that binds to the given group. The dry run - access level will be evaluated but won't be enforced. Denial on dry run - access level will be logged. The input must be the full identifier of - an access level, such as accessPolicies/123/accessLevels/new-def. + The dry run access level that binds to the given group and restricted + client applications. The dry run access level is evaluated but isn't + enforced. Denial on a dry run access level is logged. The input must be + the full identifier of an access level, such as + accessPolicies/123/accessLevels/new-def. If no + restricted-client-application-client-ids or + restricted-client-application-names are provided, then the access level + is applied to the entire organization. --level=[LEVEL,...] - The access level that binds to the given group. The input must be the - full identifier of an access level, such as - accessPolicies/123/accessLevels/abc. + The access level that binds to the given group and restricted client + applications. The input must be the full identifier of an access level, + such as accessPolicies/123/accessLevels/abc. If no + restricted-client-application-client-ids or + restricted-client-application-names are provided, then the access level + is applied to the entire organization. --organization=ORGANIZATION Parent organization for this binding. + --restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS,...] + Client IDs to which the access level is applied. + + --restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES,...] + Application names to which the access level is applied. + 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/access-context-manager/cloud-bindings/help b/gcloud/alpha/access-context-manager/cloud-bindings/help index be1d8d136..1e07a9aa0 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/help +++ b/gcloud/alpha/access-context-manager/cloud-bindings/help @@ -31,7 +31,7 @@ COMMANDS (ALPHA) List cloud access bindings under an organization. update - (ALPHA) Update a existing cloud access binding under an organization. + (ALPHA) Update an existing access binding under an organization. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/list b/gcloud/alpha/access-context-manager/cloud-bindings/list index c3621932a..8d96fe959 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/list +++ b/gcloud/alpha/access-context-manager/cloud-bindings/list @@ -15,10 +15,20 @@ EXAMPLES $ gcloud alpha access-context-manager cloud-bindings list - This command prints a list of gcpUserAccessBindings in a tabular form: + This command prints a list of Google Cloud user access bindings, + gcpUserAccessBindings, in YAML format: - NAME GROUP_KEY ACCESS_LEVEL DRY_RUN_ACCESS_LEVEL - organizations/256/gcpUserAccessBindings/b3-BhcX_Ud5N a3dad accessPolicies/9522/accessLevels/device_trusted accessPolicies/9522/accessLevels/specific_location + --- + accessLevels: + - accessPolicies/9522/accessLevels/device_trusted + dryRunAccessLevels: + - accessPolicies/9522/accessLevels/specific_location + groupKey: a3dad + name: organizations/256/gcpUserAccessBindings/b3-BhcX_Ud5N + restrictedClientApplications: + - clientId: 123.apps.googleusercontent.com + - name: Cloud Console + - name: Google Cloud SDK FLAGS Organization resource - The parent organization of the bindings you want diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/update b/gcloud/alpha/access-context-manager/cloud-bindings/update index 6f052c0ca..cc6a7d5c9 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/update +++ b/gcloud/alpha/access-context-manager/cloud-bindings/update @@ -1,19 +1,23 @@ NAME - gcloud alpha access-context-manager cloud-bindings update - update a - existing cloud access binding under an organization + gcloud alpha access-context-manager cloud-bindings update - update an + existing access binding under an organization SYNOPSIS gcloud alpha access-context-manager cloud-bindings update (--binding=BINDING : --organization=ORGANIZATION) [--dry-run-level=[DRY_RUN_LEVEL,...]] [--level=[LEVEL,...]] - [GCLOUD_WIDE_FLAG ...] + [--restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS, + ...]] + [--restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES, + ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update an existing cloud access binding. You can update the level, - dry run level or both. They can't be both empty after update. + (ALPHA) Update an existing access binding. You can update the level, dry + run level, restricted client application client IDs and restricted client + application names. They can't all be empty. EXAMPLES - To update an existing cloud access binding, run: + To update an existing access binding, run: $ gcloud alpha access-context-manager cloud-bindings update \ --binding=my-binding-id \ @@ -25,6 +29,15 @@ EXAMPLES --binding=my-binding-id --level= \ --dry-run-level=accessPolicies/123/accessLevels/new-def + To update restricted client applications, run: + + $ gcloud alpha access-context-manager cloud-bindings update \ + --binding=my-binding-id \ + --restricted-client-application-client-ids='123.apps.googleuserc\ + ontent.com' \ + --restricted-client-application-names='Cloud Console, Google + Cloud SDK' + REQUIRED FLAGS Cloud access binding resource - The cloud access binding you want to update. The arguments in this group can be used to specify the attributes @@ -62,6 +75,14 @@ OPTIONAL FLAGS binding. The input must be the full identifier of an access level, such as accessPolicies/123/accessLevels/new-abc. + --restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS,...] + The application client IDs that replace the existing application client + IDs for the restricted client applications in the given binding. + + --restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES,...] + The application names that replace the existing application names for + the restricted client applications in the given binding. + 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/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index de71d9e70..9f6385778 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -129,7 +129,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/alpha/alloydb/instances/create-secondary b/gcloud/alpha/alloydb/instances/create-secondary index 37d590dff..fd3018c7b 100644 --- a/gcloud/alpha/alloydb/instances/create-secondary +++ b/gcloud/alpha/alloydb/instances/create-secondary @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha alloydb instances create-secondary INSTANCE --cluster=CLUSTER - --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] + --region=REGION [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] + [--async] [--availability-type=AVAILABILITY_TYPE] + [--[no-]require-connectors] [--ssl-mode=SSL_MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,6 +31,16 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP + Specify to enable or disable public IP on an instance. On instance + creation only disabling public IP is allowed. If you want to enable + public IP, an instance must be created with public IP disabled first, + then update the instance to enable public IP. ASSIGN_INBOUND_PUBLIC_IP + must be (only one value is supported): + + NO_PUBLIC_IP + This disables public IP on the instance. + --async Return immediately, without waiting for the operation in progress to complete. @@ -45,6 +57,21 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --[no-]require-connectors + Enable or disable enforcing connectors only (ex: AuthProxy) connections + to the database. Use --require-connectors to enable and + --no-require-connectors to disable. + + --ssl-mode=SSL_MODE + Specify the SSL mode to use when the instance connects to the database. + Default SSL mode will match what is set on the primary instance. + SSL_MODE must be one of: + + ALLOW_UNENCRYPTED_AND_ENCRYPTED + SSL connections are optional. CA verification is not enforced. + ENCRYPTED_ONLY + SSL connections are required. CA verification is not enforced. + 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/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index ae3f206f1..ebfa7a915 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -118,7 +118,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 1abb15e2e..622daf658 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -4,9 +4,13 @@ NAME SYNOPSIS gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK - (--bind-tags-to-instances | --export-tag-mapping + (--bind-tags-to-instances | --export-exclusion-patterns + | --export-tag-mapping | --target-firewall-policy=TARGET_FIREWALL_POLICY) - [--export-terraform-script] [--tag-mapping-file=TAG_MAPPING_FILE] + [--exclusion-patterns-file=EXCLUSION_PATTERNS_FILE] + [--export-terraform-script] [--force] + [--tag-mapping-file=TAG_MAPPING_FILE] + [--terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -32,6 +36,10 @@ REQUIRED FLAGS If set, migration tool will bind secure tags to the instances with the network tags which match secure tags from the tag mapping file. + --export-exclusion-patterns + If set, migration tool will dump list of regexes used to filter VPC + Firewall out of migration. + --export-tag-mapping If set, migration tool will inspect all VPC Firewalls attached to SOURCE_NETWORK, collect all source and target tags, and store them in @@ -42,14 +50,26 @@ REQUIRED FLAGS result. OPTIONAL FLAGS + --exclusion-patterns-file=EXCLUSION_PATTERNS_FILE + Path to a file with exclusion patterns used for VPC Firewall filtering. + Each regular expression describing a single firewall naming pattern + must be placed in a single line. No leading or tailing whitespaces. + --export-terraform-script If set, migration tool will output a terraform script to create a Firewall Policy with migrated rules. + --force + If set, migration will succeed even if the tool detects that original + rule evaluation order cannot be preserved. + --tag-mapping-file=TAG_MAPPING_FILE Path to a JSON file with legacy tags and service accounts to secure tags mapping. + --terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE + Path to a file where to store generated Terraform script. + 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 132a5b471..1aac8e346 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -645,9 +645,9 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag can be repeated to specify multiple network interfaces. The following keys are allowed: @@ -701,6 +701,30 @@ FLAGS instance network interface IPv6 access config. IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 50181838f..a9a91906e 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -52,6 +52,8 @@ SYNOPSIS | --image-family=IMAGE_FAMILY] [--maintenance-policy=MAINTENANCE_POLICY | --on-host-maintenance=MAINTENANCE_POLICY] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -558,8 +560,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -595,6 +600,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -835,6 +873,32 @@ FLAGS TERMINATE The instances should be terminated. + Specifies the reservation for instances created from this template. + + --reservation=RESERVATION + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for instances created from this template. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 866452146..0e0a27f3c 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -912,8 +912,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --source-machine-image=SOURCE_MACHINE_IMAGE The name of the machine image that the instance will be created from. @@ -1261,10 +1260,10 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can - be repeated to specify multiple network interfaces. + --internal-ipv6-address, --internal-ipv6-prefix-length, + --ipv6-address, --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag + can be repeated to specify multiple network interfaces. The following keys are allowed: address @@ -1318,6 +1317,30 @@ FLAGS IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used + only when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length + from --internal-ipv6-address will be used or the default value of + 96 will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 + IP address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index dd263499f..ac1580e92 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -65,6 +65,8 @@ SYNOPSIS | --on-host-maintenance=MAINTENANCE_POLICY] [--public-dns | --no-public-dns] [--public-ptr | --no-public-ptr] [--public-ptr-domain=PUBLIC_PTR_DOMAIN | --no-public-ptr-domain] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -604,8 +606,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -641,6 +646,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -750,8 +788,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --stack-type=STACK_TYPE Specifies whether IPv6 is enabled on the default network interface. If @@ -993,6 +1030,32 @@ FLAGS record for the external IP of the instance with the PTR domain name being the DNS name of the instance. + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for the instance. RESERVATION_AFFINITY must + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/alpha/compute/instances/help b/gcloud/alpha/compute/instances/help index 3bb41c7fb..c67c70b1f 100644 --- a/gcloud/alpha/compute/instances/help +++ b/gcloud/alpha/compute/instances/help @@ -115,8 +115,8 @@ COMMANDS (ALPHA) List Compute Engine instances. move - (ALPHA) Move an instance and its attached persistent disks between - zones. + (ALPHA) (DEPRECATED) Move an instance and its attached persistent disks + between zones. patch-partner-metadata (ALPHA) Patch partner metadata. diff --git a/gcloud/alpha/compute/instances/move b/gcloud/alpha/compute/instances/move index 207242998..798f5fbcf 100644 --- a/gcloud/alpha/compute/instances/move +++ b/gcloud/alpha/compute/instances/move @@ -8,10 +8,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute instances move moves a Compute Engine virtual - machine from one zone to another. Moving a virtual machine might incur - downtime if the guest OS must be shut down in order to quiesce disk volumes - prior to snapshotting. + (ALPHA) (DEPRECATED) This command is deprecated. Please see + https://cloud.google.com/compute/docs/instances/moving-instance-across-zones + for an alternative method. + + gcloud alpha compute instances move moves a Compute Engine virtual machine + from one zone to another. Moving a virtual machine might incur downtime if + the guest OS must be shut down in order to quiesce disk volumes prior to + snapshotting. For example, running the following command moves the instance called example-instance-1 with its attached persistent disks, currently running in diff --git a/gcloud/alpha/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/alpha/compute/public-delegated-prefixes/delegated-sub-prefixes/create index 5da0aca7b..de30a1c81 100644 --- a/gcloud/alpha/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/alpha/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha compute public-delegated-prefixes delegated-sub-prefixes create NAME --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] [--create-addresses] [--delegatee-project=DELEGATEE_PROJECT] - [--description=DESCRIPTION] [--range=RANGE] + [--description=DESCRIPTION] [--mode=MODE] [--range=RANGE] [--global-public-delegated-prefix | --public-delegated-prefix-region=PUBLIC_DELEGATED_PREFIX_REGION] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +41,9 @@ REQUIRED FLAGS for. OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + Specify allocatable prefix length supported by this sub prefix. + --create-addresses Specify if the sub prefix is delegated to create address resources in the delegatee project. Default is false. @@ -51,6 +55,10 @@ OPTIONAL FLAGS --description=DESCRIPTION Description of the delegated sub prefix to create. + --mode=MODE + Specify mode for the sub prefix. MODE must be one of: DELEGATION, + EXTERNAL_IPV6_FORWARDING_RULE_CREATION. + --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. If not specified, the entire range ofthe public diff --git a/gcloud/alpha/compute/routers/add-bgp-peer b/gcloud/alpha/compute/routers/add-bgp-peer index 846a2e8cd..605c7aed1 100644 --- a/gcloud/alpha/compute/routers/add-bgp-peer +++ b/gcloud/alpha/compute/routers/add-bgp-peer @@ -8,7 +8,9 @@ SYNOPSIS [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] - [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] + [--[no-]enable-ipv6] [--[no-]enabled] + [--export-policies=[EXPORT_POLICY,...]] + [--import-policies=[IMPORT_POLICY,...]] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] @@ -87,6 +89,14 @@ OPTIONAL FLAGS terminated and all associated routing information is removed. Enabled by default. Use --enabled to enable and --no-enabled to disable. + --export-policies=[EXPORT_POLICY,...] + Comma-separated list of export policies. Passing an empty string + removes all export policies. + + --import-policies=[IMPORT_POLICY,...] + Comma-separated list of import policies. Passing an empty string + removes all import policies. + --instance=INSTANCE Router appliance instance of the BGP peer being added. @@ -134,7 +144,7 @@ OPTIONAL FLAGS --peer-ip-address=PEER_IP_ADDRESS The address of the peer router. Must be a link-local IPv4 address in - the the range 169.254.0.0/16 or an ULA IPv6 address in the range + the range 169.254.0.0/16 or an ULA IPv6 address in the range fdff:1::/64. --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS diff --git a/gcloud/alpha/compute/routers/add-route-policy b/gcloud/alpha/compute/routers/add-route-policy new file mode 100644 index 000000000..5f177bb7e --- /dev/null +++ b/gcloud/alpha/compute/routers/add-route-policy @@ -0,0 +1,66 @@ +NAME + gcloud alpha compute routers add-route-policy - add an empty route policy + to a Compute Engine router + +SYNOPSIS + gcloud alpha compute routers add-route-policy NAME + --policy-name=POLICY_NAME --policy-type=POLICY_TYPE [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers add-route-policy adds an empty route + policy to a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to update. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to add. + + --policy-type=POLICY_TYPE + Type of the route policy to add. POLICY_TYPE must be one of: + + EXPORT + The route policy is an export policy. + IMPORT + The route policy is an import policy. + +OPTIONAL FLAGS + --region=REGION + Region of the router to update. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This variant is also available: + + $ gcloud beta compute routers add-route-policy + diff --git a/gcloud/alpha/compute/routers/download-route-policy b/gcloud/alpha/compute/routers/download-route-policy new file mode 100644 index 000000000..1a8b1cd3d --- /dev/null +++ b/gcloud/alpha/compute/routers/download-route-policy @@ -0,0 +1,65 @@ +NAME + gcloud alpha compute routers download-route-policy - download a route + policy from a Compute Engine router + +SYNOPSIS + gcloud alpha compute routers download-route-policy NAME + --file-name=FILE_NAME --policy-name=POLICY_NAME + [--file-format=FILE_FORMAT] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers download-route-policy downloads a + route policy from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to export. + +REQUIRED FLAGS + --file-name=FILE_NAME + The name of the file to download the route policy config to. + + --policy-name=POLICY_NAME + Name of the route policy to download. + +OPTIONAL FLAGS + --file-format=FILE_FORMAT + Format of the file passed to --file-name. FILE_FORMAT must be one of: + json, yaml. + + --region=REGION + Region of the router to export. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This variant is also available: + + $ gcloud beta compute routers download-route-policy + diff --git a/gcloud/alpha/compute/routers/get-route-policy b/gcloud/alpha/compute/routers/get-route-policy new file mode 100644 index 000000000..7a9dc709f --- /dev/null +++ b/gcloud/alpha/compute/routers/get-route-policy @@ -0,0 +1,57 @@ +NAME + gcloud alpha compute routers get-route-policy - get a route policy from a + Compute Engine router + +SYNOPSIS + gcloud alpha compute routers get-route-policy NAME + --policy-name=POLICY_NAME [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers get-route-policy gets a route policy + from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to get. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to get. + +OPTIONAL FLAGS + --region=REGION + Region of the router to get. If not specified, you might be prompted to + select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This variant is also available: + + $ gcloud beta compute routers get-route-policy + diff --git a/gcloud/alpha/compute/routers/help b/gcloud/alpha/compute/routers/help index 719120c37..0b17d9c35 100644 --- a/gcloud/alpha/compute/routers/help +++ b/gcloud/alpha/compute/routers/help @@ -35,6 +35,9 @@ COMMANDS add-interface (ALPHA) Add an interface to a Compute Engine router. + add-route-policy + (ALPHA) Add an empty route policy to a Compute Engine router. + create (ALPHA) Create a Compute Engine router. @@ -44,24 +47,40 @@ COMMANDS describe (ALPHA) Describe a Compute Engine router. + download-route-policy + (ALPHA) Download a route policy from a Compute Engine router. + get-nat-ip-info (ALPHA) Display NAT IP information in a router. get-nat-mapping-info (ALPHA) Display NAT Mapping information in a router. + get-route-policy + (ALPHA) Get a route policy from a Compute Engine router. + get-status (ALPHA) Get status of a Compute Engine router. list (ALPHA) List Google Compute Engine routers. + list-bgp-routes + (ALPHA) List routes advertised and learned on individual BGP sessions, + both pre- and post-policy evaluation. + + list-route-policies + (ALPHA) List route policies from a Compute Engine router. + remove-bgp-peer (ALPHA) Remove a BGP peer from a Compute Engine router. remove-interface (ALPHA) Remove an interface from a Compute Engine router. + remove-route-policy + (ALPHA) Remove a route policy from a Compute Engine router. + update (ALPHA) Update a Compute Engine router. @@ -71,6 +90,9 @@ COMMANDS update-interface (ALPHA) Update an interface on a Compute Engine router. + upload-route-policy + (ALPHA) Upload a route policy into a Compute Engine router. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/routers/list-bgp-routes b/gcloud/alpha/compute/routers/list-bgp-routes new file mode 100644 index 000000000..21c7965aa --- /dev/null +++ b/gcloud/alpha/compute/routers/list-bgp-routes @@ -0,0 +1,120 @@ +NAME + gcloud alpha compute routers list-bgp-routes - list routes advertised and + learned on individual BGP sessions, both pre- and post-policy + evaluation + +SYNOPSIS + gcloud alpha compute routers list-bgp-routes NAME + --address-family=ADDRESS_FAMILY --peer=PEER + --route-direction=ROUTE_DIRECTION [--destination-range=CIDR_RANGE] + [--no-policy-applied] [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers list-bgp-routes lists routes + advertised and learned on individual BGP sessions, both pre- and + post-policy evaluation. + +POSITIONAL ARGUMENTS + NAME + Name of the router to list. + +REQUIRED FLAGS + --address-family=ADDRESS_FAMILY + Limit results to routes learned for this Address Family Identifier. + ADDRESS_FAMILY must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. + + --peer=PEER + Limit results to routes learned from this peer (name). + + --route-direction=ROUTE_DIRECTION + Limit results to routes in this direction. ROUTE_DIRECTION must be one + of: + + INBOUND + Learned routes. + OUTBOUND + Advertised routes. + +FLAGS + --destination-range=CIDR_RANGE + Limit results to prefixes. + + --policy-applied + Routes returned are post-policy evaluation. Enabled by default, use + --no-policy-applied to disable. + + --region=REGION + Region of the router to list. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. This variant is also available: + + $ gcloud beta compute routers list-bgp-routes + diff --git a/gcloud/alpha/compute/routers/list-route-policies b/gcloud/alpha/compute/routers/list-route-policies new file mode 100644 index 000000000..33a9c32b3 --- /dev/null +++ b/gcloud/alpha/compute/routers/list-route-policies @@ -0,0 +1,86 @@ +NAME + gcloud alpha compute routers list-route-policies - list route policies from + a Compute Engine router + +SYNOPSIS + gcloud alpha compute routers list-route-policies NAME [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers list-route-policies lists all route + policies from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to list. + +FLAGS + --region=REGION + Region of the router to list. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. This variant is also available: + + $ gcloud beta compute routers list-route-policies + diff --git a/gcloud/alpha/compute/routers/remove-route-policy b/gcloud/alpha/compute/routers/remove-route-policy new file mode 100644 index 000000000..7232cd11a --- /dev/null +++ b/gcloud/alpha/compute/routers/remove-route-policy @@ -0,0 +1,57 @@ +NAME + gcloud alpha compute routers remove-route-policy - remove a route policy + from a Compute Engine router + +SYNOPSIS + gcloud alpha compute routers remove-route-policy NAME + --policy-name=POLICY_NAME [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers remove-route-policy removes a route + policy from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to delete. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to be removed. + +OPTIONAL FLAGS + --region=REGION + Region of the router to delete. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This variant is also available: + + $ gcloud beta compute routers remove-route-policy + diff --git a/gcloud/alpha/compute/routers/update-bgp-peer b/gcloud/alpha/compute/routers/update-bgp-peer index 5e3d7987c..0bedbecc4 100644 --- a/gcloud/alpha/compute/routers/update-bgp-peer +++ b/gcloud/alpha/compute/routers/update-bgp-peer @@ -7,7 +7,9 @@ SYNOPSIS [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] - [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] + [--[no-]enable-ipv6] [--[no-]enabled] + [--export-policies=[EXPORT_POLICY,...]] + [--import-policies=[IMPORT_POLICY,...]] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] @@ -87,6 +89,14 @@ OPTIONAL FLAGS terminated and all associated routing information is removed. Use --enabled to enable and --no-enabled to disable. + --export-policies=[EXPORT_POLICY,...] + Comma-separated list of export policies. Passing an empty string + removes all export policies. + + --import-policies=[IMPORT_POLICY,...] + Comma-separated list of import policies. Passing an empty string + removes all import policies. + --interface=INTERFACE The name of the interface for this BGP peer. @@ -121,7 +131,7 @@ OPTIONAL FLAGS --peer-ip-address=PEER_IP_ADDRESS The address of the peer router. Must be a link-local IPv4 address in - the the range 169.254.0.0/16 or an ULA IPv6 address in the range + the range 169.254.0.0/16 or an ULA IPv6 address in the range fdff:1::/64. --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS diff --git a/gcloud/alpha/compute/routers/upload-route-policy b/gcloud/alpha/compute/routers/upload-route-policy new file mode 100644 index 000000000..838f102c3 --- /dev/null +++ b/gcloud/alpha/compute/routers/upload-route-policy @@ -0,0 +1,65 @@ +NAME + gcloud alpha compute routers upload-route-policy - upload a route policy + into a Compute Engine router + +SYNOPSIS + gcloud alpha compute routers upload-route-policy NAME --file-name=FILE_NAME + [--file-format=FILE_FORMAT] [--policy-name=POLICY_NAME] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute routers upload-route-policy uploads a route + policy into a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to upload. + +REQUIRED FLAGS + --file-name=FILE_NAME + Local path to the file defining the policy + +OPTIONAL FLAGS + --file-format=FILE_FORMAT + Format of the file passed to --file-name. FILE_FORMAT must be one of: + json, yaml. + + --policy-name=POLICY_NAME + Name of the route policy to add/replace. + + --region=REGION + Region of the router to upload. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This variant is also available: + + $ gcloud beta compute routers upload-route-policy + diff --git a/gcloud/alpha/compute/sole-tenancy/node-groups/perform-maintenance b/gcloud/alpha/compute/sole-tenancy/node-groups/perform-maintenance index 89c883555..56dabb78a 100644 --- a/gcloud/alpha/compute/sole-tenancy/node-groups/perform-maintenance +++ b/gcloud/alpha/compute/sole-tenancy/node-groups/perform-maintenance @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute sole-tenancy node-groups perform-maintenance $ gcloud beta compute sole-tenancy node-groups perform-maintenance diff --git a/gcloud/alpha/container/fleet/mesh/debug/proxy-config b/gcloud/alpha/container/fleet/mesh/debug/proxy-config index 82a5f6756..52eee7c23 100644 --- a/gcloud/alpha/container/fleet/mesh/debug/proxy-config +++ b/gcloud/alpha/container/fleet/mesh/debug/proxy-config @@ -26,7 +26,6 @@ REQUIRED FLAGS --type=TYPE Proxy configuration type to retrieve. - all Retrieves all configuration for the Envoy in the specified pod bootstrap Retrieves bootstrap configuration for the Envoy in the specified pod clusters/cluster Retrieves cluster configuration for the Envoy in the specified pod endpoints/endpoint Retrieves endpoint configuration for the Envoy in the specified pod @@ -35,8 +34,8 @@ REQUIRED FLAGS routes/route Retrieves route configuration for the Envoy in the specified pod secrets/secret Retrieves secret configuration for the Envoy in the specified pod - TYPE must be one of: all, bootstrap, cluster, clusters, endpoint, - endpoints, listener, listeners, log, route, routes, secret, secrets. + TYPE must be one of: bootstrap, cluster, clusters, endpoint, endpoints, + listener, listeners, log, route, routes, secret, secrets. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/alpha/container/hub/mesh/debug/proxy-config b/gcloud/alpha/container/hub/mesh/debug/proxy-config index d1b7c59b7..e32a2e028 100644 --- a/gcloud/alpha/container/hub/mesh/debug/proxy-config +++ b/gcloud/alpha/container/hub/mesh/debug/proxy-config @@ -26,7 +26,6 @@ REQUIRED FLAGS --type=TYPE Proxy configuration type to retrieve. - all Retrieves all configuration for the Envoy in the specified pod bootstrap Retrieves bootstrap configuration for the Envoy in the specified pod clusters/cluster Retrieves cluster configuration for the Envoy in the specified pod endpoints/endpoint Retrieves endpoint configuration for the Envoy in the specified pod @@ -35,8 +34,8 @@ REQUIRED FLAGS routes/route Retrieves route configuration for the Envoy in the specified pod secrets/secret Retrieves secret configuration for the Envoy in the specified pod - TYPE must be one of: all, bootstrap, cluster, clusters, endpoint, - endpoints, listener, listeners, log, route, routes, secret, secrets. + TYPE must be one of: bootstrap, cluster, clusters, endpoint, endpoints, + listener, listeners, log, route, routes, secret, secrets. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/alpha/dataplex/entries/create b/gcloud/alpha/dataplex/entries/create new file mode 100644 index 000000000..a362059ee --- /dev/null +++ b/gcloud/alpha/dataplex/entries/create @@ -0,0 +1,293 @@ +NAME + gcloud alpha dataplex entries create - create a Dataplex Entry resource + +SYNOPSIS + gcloud alpha dataplex entries create + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + (--entry-type=ENTRY_TYPE : --entry-type-location=ENTRY_TYPE_LOCATION + --entry-type-project=ENTRY_TYPE_PROJECT) + [--aspects=YAML_OR_JSON_FILE] + [--fully-qualified-name=FULLY_QUALIFIED_NAME] + [--parent-entry=PARENT_ENTRY] + [--entry-source-ancestors=[ANCESTORS,...] + --entry-source-create-time=DATE_TIME + --entry-source-description=DESCRIPTION + --entry-source-display-name=DISPLAY_NAME + --entry-source-labels=[KEY=VALUE,...] + --entry-source-platform=PLATFORM_NAME + --entry-source-resource=RESOURCE --entry-source-system=SYSTEM_NAME + --entry-source-update-time=DATE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Dataplex Entry resource. + +EXAMPLES + To create a Dataplex entry with name my-dataplex-entry in location + us-central1 in entry group my-entry-group and with entry type + projects/my-project/locations/us-central1/entryTypes/my-type, run: + + $ gcloud alpha dataplex entries create my-dataplex-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type + + To create a Dataplex Entry with name my-child-entry and set its parent to + an existing entry my-parent-entry, run: + + $ gcloud alpha dataplex entries create my-child-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --parent-entry \ + projects/my-project/locations/us-central1/entryGroups/\ + my-entry-group/entries/my-parent-entry + + To create a Dataplex Entry with its description, display name, ancestors, + labels and timestamps populated in its EntrySource, run: + + $ gcloud alpha dataplex entries create my-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --entry-source-description \ + 'This is a description of the Entry.' \ + --entry-source-display-name 'display name' \ + --entry-source-ancestors \ + '{"type":"projects/my-project/locations/us-central1/entryTypes/s\ + ome-type", + "name":"projects/my-project/locations/us-central1/entryGroups/my-en\ + try-group/entries/ancestor-entry"}, + {"type":"projects/my-project/locations/us-central1/entryTypes/anoth\ + er-type", + "name":"projects/my-project/locations/us-central1/entryGroups/my-en\ + try-group/entries/another-ancestor-entry"}' \ + --entry-source-labels key1=value1,key2=value2 \ + --entry-source-create-time 2024-01-01T09:39:25.160173Z \ + --entry-source-update-time 2024-01-01T09:39:25.160173Z + + To create a Dataplex Entry reading its aspects from a YAML file, run: + + $ gcloud alpha dataplex entries create my-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --aspects aspects.yaml + + The file containing the aspects has the following format: + + my-project.us-central1.my-aspect-type: + aspectType: my-project.us-central1.my-aspect-type + createTime: "2024-01-01T09:39:25.160173Z" + updateTime: "2024-01-01T09:39:25.160173Z" + data: + {} + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + Entry type resource - Arguments and flags that define the Dataplex + EntryType you want to reference. The arguments in this group can be used + to specify the attributes of this resource. + + This must be specified. + + --entry-type=ENTRY_TYPE + ID of the entry type or fully qualified identifier for the entry + type. + + To set the entry_type attribute: + ▸ provide the argument --entry-type on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entry-type-location=ENTRY_TYPE_LOCATION + The location of the EntryType resource. + + To set the entry-type-location attribute: + ▸ provide the argument --entry-type on the command line with a + fully specified name; + ▸ provide the argument --entry-type-location on the command line. + + --entry-type-project=ENTRY_TYPE_PROJECT + The project of the EntryType resource. + + To set the entry-type-project attribute: + ▸ provide the argument --entry-type on the command line with a + fully specified name; + ▸ provide the argument --entry-type-project on the command line. + +OPTIONAL FLAGS + --aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + --fully-qualified-name=FULLY_QUALIFIED_NAME + A name for the entry that can reference it in an external system. The + maximum size of the field is 4000 characters. + + Entry resource - Arguments and flags that define the parent Entry you want + to reference. 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 --parent-entry on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + To set the location attribute: + ◆ provide the argument --parent-entry on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property dataplex/location. + + To set the entry_group attribute: + ◆ provide the argument --parent-entry on the command line with a fully + specified name; + ◆ provide the argument --entry_group on the command line. + + --parent-entry=PARENT_ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument --parent-entry on the command line. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-ancestors=[ANCESTORS,...] + Information about individual items in the hierarchy of an Entry. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + --entry-source-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. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + +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. This variant is also available: + + $ gcloud dataplex entries create + diff --git a/gcloud/alpha/dataplex/entries/delete b/gcloud/alpha/dataplex/entries/delete new file mode 100644 index 000000000..93dae5804 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/delete @@ -0,0 +1,77 @@ +NAME + gcloud alpha dataplex entries delete - delete a Dataplex entry + +SYNOPSIS + gcloud alpha dataplex entries delete + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Dataplex entry. + +EXAMPLES + To delete the entry 'entry1', run: + + $ gcloud alpha dataplex entries delete entry1 \ + --entry-group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Entry 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +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: + + $ gcloud dataplex entries delete + diff --git a/gcloud/alpha/dataplex/entries/describe b/gcloud/alpha/dataplex/entries/describe new file mode 100644 index 000000000..1932536d3 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/describe @@ -0,0 +1,127 @@ +NAME + gcloud alpha dataplex entries describe - describe a Dataplex entry + +SYNOPSIS + gcloud alpha dataplex entries describe + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--aspect-types=[ASPECT_TYPES,...]] [--paths=[PATHS,...]] [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Dataplex entry. + + Displays the details of a Dataplex entry resource given a valid entry ID. + +EXAMPLES + To describe a Dataplex entry entry1 within entry group entry-group1 in + location us-central1, run: + + $ gcloud alpha dataplex entries describe entry1 \ + --entry-group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --aspect-types=[ASPECT_TYPES,...] + Limits the aspects returned to the provided aspect types. Only works if + the --view=custom is selected. + + For example, if two aspect types are specified: + "projects/projectA/locations/us-central1/my-aspect-type,projects/projectB/locations/us/my-aspect-type2" + then only aspects matching these aspect types will be returned. + + Can be further constrained by the --paths argument. + + --paths=[PATHS,...] + Limits the aspects returned to those associated with the provided paths + within the Entry. Only works if the --view=custom is selected. + + For example, if two paths are specified: "--paths=property1,property2" + then only aspects on these paths will be returned. + + To return aspects without any path, the empty (root) path can be + specified. For this "." can be used. For example, when + "--paths=.,property1" are specified, then only aspects on the path + "property1" and on the entry itself will be returned. + + Can be further constrained by --aspect-types argument. + + --view=VIEW + Controls which parts of an entry are to be returned. VIEW must be one + of: + + all + Returns all aspects. If the number of aspects would exceed 100, the + first 100 will be returned. + + basic + Returns entry only, without aspects. + custom + Returns aspects filtered based on --aspect-types AND --paths + arguments specified. When used, at least one of --aspect-types and + --paths arguments must be specified. If the number of aspects would + exceed 100, the first 100 will be returned. + + full + Default value. Returns all required aspects, as well as the keys of + all non-required aspects. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +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: + + $ gcloud dataplex entries describe + diff --git a/gcloud/alpha/dataplex/entries/help b/gcloud/alpha/dataplex/entries/help new file mode 100644 index 000000000..609dbc60b --- /dev/null +++ b/gcloud/alpha/dataplex/entries/help @@ -0,0 +1,49 @@ +NAME + gcloud alpha dataplex entries - manage Dataplex Catalog Entries resources + +SYNOPSIS + gcloud alpha dataplex entries COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Dataplex Catalog Entries resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Dataplex Entry resource. + + delete + (ALPHA) Delete a Dataplex entry. + + describe + (ALPHA) Describe a Dataplex entry. + + list + (ALPHA) List Dataplex entries. + + lookup + (ALPHA) Lookup a Dataplex entry. + + remove-aspects + (ALPHA) Remove aspects from a Dataplex Entry. + + update + (ALPHA) Update a Dataplex Entry. + + update-aspects + (ALPHA) Add or update aspects for a Dataplex Entry. + +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: + + $ gcloud dataplex entries + diff --git a/gcloud/alpha/dataplex/entries/list b/gcloud/alpha/dataplex/entries/list new file mode 100644 index 000000000..fdfdbfcb8 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/list @@ -0,0 +1,103 @@ +NAME + gcloud alpha dataplex entries list - list Dataplex entries + +SYNOPSIS + gcloud alpha dataplex entries list + (--entry-group=ENTRY_GROUP : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Dataplex entries in an entry group. + +EXAMPLES + To List the entries in entry group 'entry-group1', run: + + $ gcloud alpha dataplex entries list --entry-group=entry-group1 \ + --location=us-central1 --project=test-project + +REQUIRED FLAGS + Entry group resource - Example Entry Group to list all contained Entries. + 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 --entry-group 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. + + --entry-group=ENTRY_GROUP + ID of the entry group or fully qualified identifier for the entry + group. + + To set the entry-group attribute: + ▸ provide the argument --entry-group on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument --entry-group on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +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: + + $ gcloud dataplex entries list + diff --git a/gcloud/alpha/dataplex/entries/lookup b/gcloud/alpha/dataplex/entries/lookup new file mode 100644 index 000000000..aff53d107 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/lookup @@ -0,0 +1,131 @@ +NAME + gcloud alpha dataplex entries lookup - lookup a Dataplex entry + +SYNOPSIS + gcloud alpha dataplex entries lookup + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--aspect-types=[ASPECT_TYPES,...]] [--paths=[PATHS,...]] [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lookup a Dataplex entry. + + Displays the details of a Dataplex entry resource given a valid entry ID. + Unlike describe, where the Dataplex permission is required for access, for + lookup the permission from the original source system is required on the + entry instead. For example, if the source is a BigQuery table, you need the + bigquery.tables.get permission to lookup an entry. + +EXAMPLES + To lookup a Dataplex entry entry1 within entry group entry-group1 in + location us-central1, run: + + $ gcloud alpha dataplex entries lookup entry1 \ + --entry-group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to lookup. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --aspect-types=[ASPECT_TYPES,...] + Limits the aspects returned to the provided aspect types. Only works if + the --view=custom is selected. + + For example, if two aspect types are specified: + "projects/projectA/locations/us-central1/my-aspect-type,projects/projectB/locations/us/my-aspect-type2" + then only aspects matching these aspect types will be returned. + + Can be further constrained by the --paths argument. + + --paths=[PATHS,...] + Limits the aspects returned to those associated with the provided paths + within the Entry. Only works if the --view=custom is selected. + + For example, if two paths are specified: "--paths=property1,property2" + then only aspects on these paths will be returned. + + To return aspects without any path, the empty (root) path can be + specified. For this "." can be used. For example, when + "--paths=.,property1" are specified, then only aspects on the path + "property1" and on the entry itself will be returned. + + Can be further constrained by --aspect-types argument. + + --view=VIEW + Controls which parts of an entry are to be returned. VIEW must be one + of: + + all + Returns all aspects. If the number of aspects would exceed 100, the + first 100 will be returned. + + basic + Returns entry only, without aspects. + custom + Returns aspects filtered based on --aspect-types AND --paths + arguments specified. When used, at least one of --aspect-types and + --paths arguments must be specified. If the number of aspects would + exceed 100, the first 100 will be returned. + + full + Default value. Returns all required aspects, as well as the keys of + all non-required aspects. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +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: + + $ gcloud dataplex entries lookup + diff --git a/gcloud/alpha/dataplex/entries/remove-aspects b/gcloud/alpha/dataplex/entries/remove-aspects new file mode 100644 index 000000000..70dd1a0e2 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/remove-aspects @@ -0,0 +1,113 @@ +NAME + gcloud alpha dataplex entries remove-aspects - remove aspects from a + Dataplex Entry + +SYNOPSIS + gcloud alpha dataplex entries remove-aspects + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + --keys=[ASPECT_TYPE@PATH,...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove aspects from a Dataplex Entry. + +EXAMPLES + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud alpha dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --keys='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud alpha dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --keys='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud alpha dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --keys=test-project.us-central1.some-aspect-type@Schema.column1,\ + test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --keys=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + +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. This variant is also available: + + $ gcloud dataplex entries remove-aspects + diff --git a/gcloud/alpha/dataplex/entries/update b/gcloud/alpha/dataplex/entries/update new file mode 100644 index 000000000..e57108149 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/update @@ -0,0 +1,295 @@ +NAME + gcloud alpha dataplex entries update - update a Dataplex Entry + +SYNOPSIS + gcloud alpha dataplex entries update + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--remove-aspects=[ASPECT_TYPE@PATH,...]] + [--update-aspects=YAML_OR_JSON_FILE] + [--clear-fully-qualified-name + | --fully-qualified-name=FULLY_QUALIFIED_NAME] + [--entry-source-update-time=DATE_TIME + : --clear-entry-source-create-time + | --entry-source-create-time=DATE_TIME + --clear-entry-source-description + | --entry-source-description=DESCRIPTION + --clear-entry-source-display-name + | --entry-source-display-name=DISPLAY_NAME + --clear-entry-source-labels + | --entry-source-labels=[KEY=VALUE,...] --clear-entry-source-platform + | --entry-source-platform=PLATFORM_NAME --clear-entry-source-resource + | --entry-source-resource=RESOURCE --clear-entry-source-system + | --entry-source-system=SYSTEM_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update specified fields in a given Dataplex Entry. + +EXAMPLES + To update fully qualified name (FQN) of an entry, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --fully-qualified-name='custom:a.b.c' + + To update description of an entry, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --entry-source-description='Updated description' \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To clear the description of an entry, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --clear-entry-source-description \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To add or update aspects from the YAML/JSON file, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --update-aspects=path-to-a-file-with-aspects.json + + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --remove-aspects='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --remove-aspects='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud alpha dataplex entries update entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --remove-aspects=test-project.us-central1.some-aspect-type@Schem\ + a.column1,test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --remove-aspects=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + --update-aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + At most one of these can be specified: + + --clear-fully-qualified-name + Clear the FQN for the Entry. + + --fully-qualified-name=FULLY_QUALIFIED_NAME + FQN, a name for the entry that can reference it in an external + system. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + At most one of these can be specified: + + --clear-entry-source-create-time + Clear the value for the create_time field in the Entry Source. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-description + Clear the value for the description field in the Entry Source. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + At most one of these can be specified: + + --clear-entry-source-display-name + Clear the value for the display_name field in the Entry Source. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + At most one of these can be specified: + + --clear-entry-source-labels + Clear the labels for the Entry Source. + + --entry-source-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. + + At most one of these can be specified: + + --clear-entry-source-platform + Clear the value for the platform field in the Entry Source. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + At most one of these can be specified: + + --clear-entry-source-resource + Clear the value for the resource field in the Entry Source. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-system + Clear the value for the system field in the Entry Source. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + +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. This variant is also available: + + $ gcloud dataplex entries update + diff --git a/gcloud/alpha/dataplex/entries/update-aspects b/gcloud/alpha/dataplex/entries/update-aspects new file mode 100644 index 000000000..dfabeb7c2 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/update-aspects @@ -0,0 +1,130 @@ +NAME + gcloud alpha dataplex entries update-aspects - add or update aspects for a + Dataplex Entry + +SYNOPSIS + gcloud alpha dataplex entries update-aspects + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + --aspects=YAML_OR_JSON_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add or update aspects for a Dataplex Entry. + +EXAMPLES + To add or update aspects for the Dataplex entry entry1 within the entry + group entry-group1 in location us-central1 from the YAML/JSON file, run: + + $ gcloud alpha dataplex entries update-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --aspects=path-to-a-file-with-aspects.json + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + +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. This variant is also available: + + $ gcloud dataplex entries update-aspects + diff --git a/gcloud/alpha/dataplex/help b/gcloud/alpha/dataplex/help index 4c70667d4..99e9896e9 100644 --- a/gcloud/alpha/dataplex/help +++ b/gcloud/alpha/dataplex/help @@ -30,6 +30,9 @@ GROUPS datascans (ALPHA) Manage Dataplex Datascan. + entries + (ALPHA) Manage Dataplex Catalog Entries resources. + environments (ALPHA) Manage Dataplex Environments. diff --git a/gcloud/alpha/developer-connect/connections/create b/gcloud/alpha/developer-connect/connections/create new file mode 100644 index 000000000..a6e5d7b9f --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/create @@ -0,0 +1,190 @@ +NAME + gcloud alpha developer-connect connections create - create connections + +SYNOPSIS + gcloud alpha developer-connect connections create + (CONNECTION : --location=LOCATION) [--annotations=[ANNOTATIONS,...]] + [--async] [--disabled] [--etag=ETAG] [--labels=[LABELS,...]] + [--github-config-github-app=GITHUB_CONFIG_GITHUB_APP + : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID (--github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION : --secret=SECRET)] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a connection + +EXAMPLES + To create the connection, run: + + $ gcloud alpha developer-connect connections create + +POSITIONAL ARGUMENTS + Connection resource - Identifier. The resource name of the connection, in + the format + projects/{project}/locations/{location}/connections/{connection_id}. 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 connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 + --annotations=[ANNOTATIONS,...] + Allows clients to store small amounts of arbitrary data. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --annotations=string=string + + JSON Example: + + --annotations='{"string": "string"}' + + File Example: + + --annotations=path_to_file.(yaml|json) + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --disabled + If disabled is set to true, functionality is disabled for this + connection. Repository based API methods and webhooks processing for + repositories in this connection will be disabled. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + Arguments for the connection config. + + Configuration for connections to github.com. + + --github-config-github-app=GITHUB_CONFIG_GITHUB_APP + The GitHub Application that was installed to the GitHub user or + organization. GITHUB_CONFIG_GITHUB_APP must be one of: + + developer-connect + The Developer Connect GitHub Application. + firebase + The Firebase GitHub Application. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID + GitHub App installation id. + + Represents an OAuth token of the account that authorized the + Connection, and associated metadata. + + SecretVersion resource - A SecretManager resource containing the + OAuth token that authorizes the connection. Format: + projects/*/secrets/*/versions/*. 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 + --github-config-authorizer-credential-oauth-token-secret-version + 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. + + --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for the + secretVersion. + + To set the secret-version attribute: + ▹ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --secret=SECRET + secrets TBD + + To set the secret attribute: + ▹ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ▹ provide the argument --secret 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/delete b/gcloud/alpha/developer-connect/connections/delete new file mode 100644 index 000000000..6692341cf --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/delete @@ -0,0 +1,94 @@ +NAME + gcloud alpha developer-connect connections delete - delete connections + +SYNOPSIS + gcloud alpha developer-connect connections delete + (CONNECTION : --location=LOCATION) [--async] [--etag=ETAG] + [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a connection + +EXAMPLES + To delete the connection, run: + + $ gcloud alpha developer-connect connections delete + +POSITIONAL ARGUMENTS + Connection resource - Name of the 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: + ◆ 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 connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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. + + --etag=ETAG + The current etag of the Connection. If an etag is provided and does not + match the current etag of the Connection, deletion will be blocked and + an ABORTED error will be returned. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --validate-only + If set, validate the request, but do not actually post it. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/describe b/gcloud/alpha/developer-connect/connections/describe new file mode 100644 index 000000000..3d4a8d020 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha developer-connect connections describe - describe connections + +SYNOPSIS + gcloud alpha developer-connect connections describe + (CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a connection + +EXAMPLES + To describe the connection, run: + + $ gcloud alpha developer-connect connections describe + +POSITIONAL ARGUMENTS + Connection resource - Name of the 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: + ◆ 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 connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/create b/gcloud/alpha/developer-connect/connections/git-repository-links/create new file mode 100644 index 000000000..b836a2432 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/create @@ -0,0 +1,136 @@ +NAME + gcloud alpha developer-connect connections git-repository-links create - + create gitRepositoryLinks + +SYNOPSIS + gcloud alpha developer-connect connections git-repository-links create + (GIT_REPOSITORY_LINK : --connection=CONNECTION --location=LOCATION) + --clone-uri=CLONE_URI [--annotations=[ANNOTATIONS,...]] [--async] + [--etag=ETAG] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a gitRepositoryLink + +EXAMPLES + To create the gitRepositoryLink, run: + + $ gcloud alpha developer-connect connections git-repository-links \ create + +POSITIONAL ARGUMENTS + GitRepositoryLink resource - Identifier. Resource name of the repository, + in the format projects/*/locations/*/connections/*/gitRepositoryLinks/*. + 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 git_repository_link 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. + + GIT_REPOSITORY_LINK + ID of the gitRepositoryLink or fully qualified identifier for the + gitRepositoryLink. + + To set the git_repository_link attribute: + ▸ provide the argument git_repository_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + connections TBD + + To set the connection attribute: + ▸ provide the argument git_repository_link on the command line with + a fully specified name; + ▸ provide the argument --connection on the command line. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument git_repository_link on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --clone-uri=CLONE_URI + Git Clone URI. + +OPTIONAL FLAGS + --annotations=[ANNOTATIONS,...] + Allows clients to store small amounts of arbitrary data. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --annotations=string=string + + JSON Example: + + --annotations='{"string": "string"}' + + File Example: + + --annotations=path_to_file.(yaml|json) + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/delete b/gcloud/alpha/developer-connect/connections/git-repository-links/delete new file mode 100644 index 000000000..8a09e4d16 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/delete @@ -0,0 +1,105 @@ +NAME + gcloud alpha developer-connect connections git-repository-links delete - + delete gitRepositoryLinks + +SYNOPSIS + gcloud alpha developer-connect connections git-repository-links delete + (GIT_REPOSITORY_LINK : --connection=CONNECTION --location=LOCATION) + [--async] [--etag=ETAG] [--request-id=REQUEST_ID] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a gitRepositoryLink + +EXAMPLES + To delete the gitRepositoryLink, run: + + $ gcloud alpha developer-connect connections git-repository-links \ delete + +POSITIONAL ARGUMENTS + GitRepositoryLink resource - Name of the 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: + ◆ provide the argument git_repository_link 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. + + GIT_REPOSITORY_LINK + ID of the gitRepositoryLink or fully qualified identifier for the + gitRepositoryLink. + + To set the git_repository_link attribute: + ▸ provide the argument git_repository_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + connections TBD + + To set the connection attribute: + ▸ provide the argument git_repository_link on the command line with + a fully specified name; + ▸ provide the argument --connection on the command line. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument git_repository_link 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. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --validate-only + If set, validate the request, but do not actually post it. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/describe b/gcloud/alpha/developer-connect/connections/git-repository-links/describe new file mode 100644 index 000000000..d81d27209 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/describe @@ -0,0 +1,76 @@ +NAME + gcloud alpha developer-connect connections git-repository-links describe - + describe gitRepositoryLinks + +SYNOPSIS + gcloud alpha developer-connect connections git-repository-links describe + (GIT_REPOSITORY_LINK : --connection=CONNECTION --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a gitRepositoryLink + +EXAMPLES + To describe the gitRepositoryLink, run: + + $ gcloud alpha developer-connect connections git-repository-links \ describe + +POSITIONAL ARGUMENTS + GitRepositoryLink resource - Name of the 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: + ◆ provide the argument git_repository_link 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. + + GIT_REPOSITORY_LINK + ID of the gitRepositoryLink or fully qualified identifier for the + gitRepositoryLink. + + To set the git_repository_link attribute: + ▸ provide the argument git_repository_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + connections TBD + + To set the connection attribute: + ▸ provide the argument git_repository_link on the command line with + a fully specified name; + ▸ provide the argument --connection on the command line. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument git_repository_link 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/help b/gcloud/alpha/developer-connect/connections/git-repository-links/help new file mode 100644 index 000000000..a288f0595 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha developer-connect connections git-repository-links - manage + Git Repository Link resources + +SYNOPSIS + gcloud alpha developer-connect connections git-repository-links COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Git Repository Link resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create gitRepositoryLinks. + + delete + (ALPHA) Delete gitRepositoryLinks. + + describe + (ALPHA) Describe gitRepositoryLinks. + + list + (ALPHA) List gitRepositoryLinks. + +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. + diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/list b/gcloud/alpha/developer-connect/connections/git-repository-links/list new file mode 100644 index 000000000..a09353eb4 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/list @@ -0,0 +1,101 @@ +NAME + gcloud alpha developer-connect connections git-repository-links list - list + gitRepositoryLinks + +SYNOPSIS + gcloud alpha developer-connect connections git-repository-links list + (--connection=CONNECTION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List gitRepositoryLinks + +EXAMPLES + To list all gitRepositoryLinks, run: + + $ gcloud alpha developer-connect connections git-repository-links \ list + +REQUIRED FLAGS + Connection resource - Parent value for ListGitRepositoryLinksRequest 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=CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument --connection on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + locations TBD + + 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. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/help b/gcloud/alpha/developer-connect/connections/help new file mode 100644 index 000000000..f4a8d5e08 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/help @@ -0,0 +1,45 @@ +NAME + gcloud alpha developer-connect connections - manage Connection resources + +SYNOPSIS + gcloud alpha developer-connect connections GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Connection resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + git-repository-links + (ALPHA) Manage Git Repository Link resources. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create connections. + + delete + (ALPHA) Delete connections. + + describe + (ALPHA) Describe connections. + + list + (ALPHA) List connections. + + update + (ALPHA) Update connections. + +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. + diff --git a/gcloud/alpha/developer-connect/connections/list b/gcloud/alpha/developer-connect/connections/list new file mode 100644 index 000000000..6a669ef35 --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha developer-connect connections list - list connections + +SYNOPSIS + gcloud alpha developer-connect connections list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List connections + +EXAMPLES + To list all connections, run: + + $ gcloud alpha developer-connect connections list + +REQUIRED FLAGS + Location resource - Parent value for ListConnectionsRequest 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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update new file mode 100644 index 000000000..1051fd86e --- /dev/null +++ b/gcloud/alpha/developer-connect/connections/update @@ -0,0 +1,250 @@ +NAME + gcloud alpha developer-connect connections update - update connections + +SYNOPSIS + gcloud alpha developer-connect connections update + (CONNECTION : --location=LOCATION) [--async] [--disabled] [--etag=ETAG] + [--annotations=[ANNOTATIONS,...] + | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations + | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + [--github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID + [--github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION : --secret=SECRET]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a connection + +EXAMPLES + To update the connection, run: + + $ gcloud alpha developer-connect connections update + +POSITIONAL ARGUMENTS + Connection resource - Identifier. The resource name of the connection, in + the format + projects/{project}/locations/{location}/connections/{connection_id}. 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 connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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. + + --disabled + If disabled is set to true, functionality is disabled for this + connection. Repository based API methods and webhooks processing for + repositories in this connection will be disabled. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + Update annotations. + + At most one of these can be specified: + + --annotations=[ANNOTATIONS,...] + Set annotations to new value. Allows clients to store small amounts + of arbitrary data. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --annotations=string=string + + JSON Example: + + --annotations='{"string": "string"}' + + File Example: + + --annotations=path_to_file.(yaml|json) + + --update-annotations=[UPDATE_ANNOTATIONS,...] + Update annotations value or add key value pair. Allows clients to + store small amounts of arbitrary data. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-annotations=string=string + + JSON Example: + + --update-annotations='{"string": "string"}' + + File Example: + + --update-annotations=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-annotations + Clear annotations value and set to empty map. + + --remove-annotations=[__REMOVE_ANNOTATIONS,...] + Remove existing value from map annotations. + + Arguments for the connection config. + + Configuration for connections to github.com. + + --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID + GitHub App installation id. + + Represents an OAuth token of the account that authorized the + Connection, and associated metadata. + + SecretVersion resource - A SecretManager resource containing the + OAuth token that authorizes the connection. Format: + projects/*/secrets/*/versions/*. 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 + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ set the property core/project; + ◇ provide the argument --project on the command line. + + --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for the + secretVersion. + + To set the secret-version attribute: + ▹ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --secret=SECRET + secrets TBD + + To set the secret attribute: + ▹ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ▹ provide the argument --secret on the command line. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/help b/gcloud/alpha/developer-connect/help new file mode 100644 index 000000000..9f4815c1a --- /dev/null +++ b/gcloud/alpha/developer-connect/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha developer-connect - manage Developer Connect resources + +SYNOPSIS + gcloud alpha developer-connect GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Developer Connect resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + connections + (ALPHA) Manage Connection resources. + + operations + (ALPHA) Manage Operation resources. + +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. + diff --git a/gcloud/alpha/developer-connect/operations/cancel b/gcloud/alpha/developer-connect/operations/cancel new file mode 100644 index 000000000..7fb18da3f --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/cancel @@ -0,0 +1,65 @@ +NAME + gcloud alpha developer-connect operations cancel - cancel operations + +SYNOPSIS + gcloud alpha developer-connect operations cancel + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel an operation + +EXAMPLES + To cancel the operation, run: + + $ gcloud alpha developer-connect operations cancel + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to be cancelled. + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/operations/delete b/gcloud/alpha/developer-connect/operations/delete new file mode 100644 index 000000000..b5301d6bd --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/delete @@ -0,0 +1,65 @@ +NAME + gcloud alpha developer-connect operations delete - delete operations + +SYNOPSIS + gcloud alpha developer-connect operations delete + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an operation + +EXAMPLES + To delete the operation, run: + + $ gcloud alpha developer-connect operations delete + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to be deleted. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/operations/describe b/gcloud/alpha/developer-connect/operations/describe new file mode 100644 index 000000000..ba762ae07 --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha developer-connect operations describe - describe operations + +SYNOPSIS + gcloud alpha developer-connect operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an operation + +EXAMPLES + To describe the operation, run: + + $ gcloud alpha developer-connect operations describe + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation 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: + ◆ 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/operations/help b/gcloud/alpha/developer-connect/operations/help new file mode 100644 index 000000000..76b811b40 --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha developer-connect operations - manage Operation resources + +SYNOPSIS + gcloud alpha developer-connect operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Operation resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel operations. + + delete + (ALPHA) Delete operations. + + describe + (ALPHA) Describe operations. + + list + (ALPHA) List operations. + + wait + (ALPHA) Wait operations. + +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. + diff --git a/gcloud/alpha/developer-connect/operations/list b/gcloud/alpha/developer-connect/operations/list new file mode 100644 index 000000000..0ee7fff64 --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha developer-connect operations list - list operations + +SYNOPSIS + gcloud alpha developer-connect operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List operations + +EXAMPLES + To list all operations, run: + + $ gcloud alpha developer-connect operations list + +REQUIRED FLAGS + Location resource - The name of the operation's parent resource. 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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/developer-connect/operations/wait b/gcloud/alpha/developer-connect/operations/wait new file mode 100644 index 000000000..d93b1c37a --- /dev/null +++ b/gcloud/alpha/developer-connect/operations/wait @@ -0,0 +1,65 @@ +NAME + gcloud alpha developer-connect operations wait - wait operations + +SYNOPSIS + gcloud alpha developer-connect operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Wait an operation + +EXAMPLES + To wait the operation, run: + + $ gcloud alpha developer-connect operations wait + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to wait on. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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. + diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 7560bb27f..04a6a34a5 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -442,6 +442,12 @@ FLAGS --clear-max-instances Clears the maximum instances setting for the function. + If it's any 2nd gen function or a 1st gen HTTP function, this flag + sets maximum instances to 0, which means there is no limit to maximum + instances. If it's an event-driven 1st gen function, this flag sets + maximum instances to 3000, which is the default value for 1st gen + functions. + --max-instances=MAX_INSTANCES Sets the maximum number of instances for the function. A function execution that would exceed max-instances times out. diff --git a/gcloud/alpha/functions/help b/gcloud/alpha/functions/help index 5294f3832..f07ccb10c 100644 --- a/gcloud/alpha/functions/help +++ b/gcloud/alpha/functions/help @@ -69,9 +69,6 @@ COMMANDS set-iam-policy (ALPHA) Sets IAM policy for a Google Cloud Function. - upgrade - (ALPHA) Upgrade a 1st gen Cloud Function to the 2nd gen environment. - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/functions/upgrade b/gcloud/alpha/functions/upgrade deleted file mode 100644 index 0578304cd..000000000 --- a/gcloud/alpha/functions/upgrade +++ /dev/null @@ -1,105 +0,0 @@ -NAME - gcloud alpha functions upgrade - upgrade a 1st gen Cloud Function to the - 2nd gen environment - -SYNOPSIS - gcloud alpha functions upgrade (NAME : --region=REGION) - [--abort | --commit | --redirect-traffic | --rollback-traffic - | --setup-config] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Upgrade a 1st gen Cloud Function to the 2nd gen environment. - -EXAMPLES - To start the upgrade process for a 1st gen function foo and create a 2nd - gen copy, run: - - $ gcloud alpha functions upgrade foo --setup-config - - Once you are ready to redirect traffic to the 2nd gen copy, run: - - $ gcloud alpha functions upgrade foo --redirect-traffic - - If you find you need to do more local testing you can rollback traffic to - the 1st gen copy: - - $ gcloud alpha functions upgrade foo --rollback-traffic - - Once you're ready to finish upgrading and delete the 1st gen copy, run: - - $ gcloud alpha functions upgrade foo --commit - - You can abort the upgrade process at any time by running: - - $ gcloud alpha functions upgrade foo --abort - -POSITIONAL ARGUMENTS - Function resource - The Cloud function name to upgrade. 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 argument 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. - -FLAGS - At most one of these can be specified: - - --abort - Undoes all steps of the upgrade process done so far. All traffic will - point to the original 1st gen function copy and the 2nd gen function - copy will be deleted. - - --commit - Finishes the upgrade process and permanently deletes the original 1st - gen copy of the function. - - --redirect-traffic - Redirects production traffic to the 2nd gen copy of the function. - - --rollback-traffic - Rolls back production traffic to the original 1st gen copy of the - function. The 2nd gen copy will still be available for testing. - - --setup-config - Sets up the function upgrade config by creating a 2nd gen copy of the - function's code and configuration. - -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. - diff --git a/gcloud/alpha/kms/keys/create b/gcloud/alpha/kms/keys/create index 1c2609e25..fe83113cd 100644 --- a/gcloud/alpha/kms/keys/create +++ b/gcloud/alpha/kms/keys/create @@ -168,19 +168,19 @@ OPTIONAL FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --destroy-scheduled-duration=DESTROY_SCHEDULED_DURATION The amount of time that versions of the key should spend in the diff --git a/gcloud/alpha/kms/keys/update b/gcloud/alpha/kms/keys/update index ed8b90062..a39ad3e4f 100644 --- a/gcloud/alpha/kms/keys/update +++ b/gcloud/alpha/kms/keys/update @@ -117,19 +117,19 @@ FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --next-rotation-time=NEXT_ROTATION_TIME Next automatic rotation time of the key. See $ gcloud topic datetimes diff --git a/gcloud/alpha/kms/keys/versions/import b/gcloud/alpha/kms/keys/versions/import index db5a88640..5438988c0 100644 --- a/gcloud/alpha/kms/keys/versions/import +++ b/gcloud/alpha/kms/keys/versions/import @@ -32,7 +32,7 @@ REQUIRED FLAGS about supported algorithms, see https://cloud.google.com/kms/docs/algorithms. ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, - aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, + aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, diff --git a/gcloud/alpha/logging/views/describe b/gcloud/alpha/logging/views/describe index 2bbf9e42f..a12b82a88 100644 --- a/gcloud/alpha/logging/views/describe +++ b/gcloud/alpha/logging/views/describe @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Displays information about a view. + (ALPHA) Displays information about a log view. EXAMPLES To describe a view in a project, run: diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index e7ccace73..1e6944d56 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -7,9 +7,10 @@ SYNOPSIS (STORAGE_POOL : --location=LOCATION) --capacity=CAPACITY --network=[name=NAME],[psa-range=PSA-RANGE] --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] - [--async] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] + [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--replica-zone=REPLICA_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Storage Pool to contain Volumes with a specified Service @@ -138,6 +139,10 @@ OPTIONAL FLAGS To set the active_directory attribute: ▸ provide the argument --active-directory on the command line. + --allow-auto-tiering=ALLOW_AUTO_TIERING + Boolean flag indicating whether Storage Pool is allowed to use + auto-tiering + --async Return immediately, without waiting for the operation in progress to complete. @@ -180,6 +185,12 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --replica-zone=REPLICA_ZONE + String indicating replica zone for the Storage Pool + + --zone=ZONE + String indicating active zone of the Storage Pool + 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/netapp/storage-pools/help b/gcloud/alpha/netapp/storage-pools/help index da5cc7929..c271ec325 100644 --- a/gcloud/alpha/netapp/storage-pools/help +++ b/gcloud/alpha/netapp/storage-pools/help @@ -28,6 +28,9 @@ COMMANDS list (ALPHA) List Cloud NetApp Storage Pools. + switch + (ALPHA) Switch a Regional Cloud NetApp SO Storage Pool zone. + update (ALPHA) Update a Cloud NetApp Storage Pool. diff --git a/gcloud/alpha/netapp/storage-pools/switch b/gcloud/alpha/netapp/storage-pools/switch new file mode 100644 index 000000000..7dd15552a --- /dev/null +++ b/gcloud/alpha/netapp/storage-pools/switch @@ -0,0 +1,78 @@ +NAME + gcloud alpha netapp storage-pools switch - switch a Regional Cloud NetApp + SO Storage Pool zone + +SYNOPSIS + gcloud alpha netapp storage-pools switch + (STORAGE_POOL : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Switch a Regional Cloud NetApp SO Storage Pool zone. + +EXAMPLES + The following command switches zone of a Storage Pool named NAME using the + required arguments: + + $ gcloud alpha netapp storage-pools switch NAME \ + --location=us-central1 + + To switch zone of a Storage Pool named NAME asynchronously, run the + following command: + + $ gcloud alpha netapp storage-pools switch NAME \ + --location=us-central1 --async + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to switch. 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 storage_pool 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. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +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. + +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: + + $ gcloud beta netapp storage-pools switch + diff --git a/gcloud/alpha/netapp/storage-pools/update b/gcloud/alpha/netapp/storage-pools/update index 88e0375ef..6d1ea49f6 100644 --- a/gcloud/alpha/netapp/storage-pools/update +++ b/gcloud/alpha/netapp/storage-pools/update @@ -5,9 +5,12 @@ NAME SYNOPSIS gcloud alpha netapp storage-pools update (STORAGE_POOL : --location=LOCATION) - [--active-directory=ACTIVE_DIRECTORY] [--async] [--capacity=CAPACITY] - [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--active-directory=ACTIVE_DIRECTORY] + [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--capacity=CAPACITY] [--description=DESCRIPTION] + [--replica-zone=REPLICA_ZONE] [--update-labels=[KEY=VALUE,...]] + [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Updates a Storage Pool with given arguments @@ -77,6 +80,10 @@ FLAGS To set the active_directory attribute: ▸ provide the argument --active-directory on the command line. + --allow-auto-tiering=ALLOW_AUTO_TIERING + Boolean flag indicating whether Storage Pool is allowed to use + auto-tiering + --async Return immediately, without waiting for the operation in progress to complete. @@ -88,6 +95,9 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --replica-zone=REPLICA_ZONE + String indicating replica zone for the Storage Pool + --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. @@ -97,6 +107,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --zone=ZONE + String indicating active zone of the Storage Pool + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/netapp/volumes/create b/gcloud/alpha/netapp/volumes/create index d6b3efec3..4815185c1 100644 --- a/gcloud/alpha/netapp/volumes/create +++ b/gcloud/alpha/netapp/volumes/create @@ -31,6 +31,7 @@ SYNOPSIS [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--source-snapshot=SOURCE_SNAPSHOT] + [--tiering-policy=[tier-action=ENABLED|PAUSED,...]] [--unix-permissions=UNIX_PERMISSIONS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -231,6 +232,18 @@ OPTIONAL FLAGS To set the snapshot attribute: ▸ provide the argument --source-snapshot on the command line. + --tiering-policy=[tier-action=ENABLED|PAUSED,...] + Tiering Policy contains auto tiering policy on a volume. + + Tiering Policy will have the following format + --tiering-policy=tier-action=TIER_ACTION, + cooling-threshold-days=COOLING_THRESHOLD_DAYS + + tier-action is an enum, supported values are ENABLED or PAUSED, + cooling-threshold-days is an integer represents time in days to mark + the volume's data block as cold and make it eligible for tiering, can + be range from 7-183. Default is 31. + --unix-permissions=UNIX_PERMISSIONS Unix permissions the mount point will be created with. Unix permissions are only applicable with NFS protocol only diff --git a/gcloud/alpha/netapp/volumes/update b/gcloud/alpha/netapp/volumes/update index a13b67aa8..fe1893287 100644 --- a/gcloud/alpha/netapp/volumes/update +++ b/gcloud/alpha/netapp/volumes/update @@ -29,6 +29,7 @@ SYNOPSIS [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--source-snapshot=SOURCE_SNAPSHOT] [--storage-pool=STORAGE_POOL] + [--tiering-policy=[tier-action=ENABLED|PAUSED,...]] [--unix-permissions=UNIX_PERMISSIONS] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -202,6 +203,18 @@ FLAGS To set the storage_pool attribute: ▸ provide the argument --storage-pool on the command line. + --tiering-policy=[tier-action=ENABLED|PAUSED,...] + Tiering Policy contains auto tiering policy on a volume. + + Tiering Policy will have the following format + --tiering-policy=tier-action=TIER_ACTION, + cooling-threshold-days=COOLING_THRESHOLD_DAYS + + tier-action is an enum, supported values are ENABLED or PAUSED, + cooling-threshold-days is an integer represents time in days to mark + the volume's data block as cold and make it eligible for tiering, can + be range from 7-183. Default is 31. + --unix-permissions=UNIX_PERMISSIONS Unix permissions the mount point will be created with. Unix permissions are only applicable with NFS protocol only diff --git a/gcloud/alpha/number-registry/help b/gcloud/alpha/number-registry/help new file mode 100644 index 000000000..4cca5770a --- /dev/null +++ b/gcloud/alpha/number-registry/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha number-registry - manage cloud number registry resources + +SYNOPSIS + gcloud alpha number-registry GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage cloud number registry resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + operations + (ALPHA) Manage Operation resources. + + registry-books + (ALPHA) Manage registry book resources. + +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. + diff --git a/gcloud/alpha/number-registry/operations/cancel b/gcloud/alpha/number-registry/operations/cancel new file mode 100644 index 000000000..a200d92e7 --- /dev/null +++ b/gcloud/alpha/number-registry/operations/cancel @@ -0,0 +1,64 @@ +NAME + gcloud alpha number-registry operations cancel - cancel operations + +SYNOPSIS + gcloud alpha number-registry operations cancel + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel an operation + +EXAMPLES + To cancel the operation, run: + + $ gcloud alpha number-registry operations cancel + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to be cancelled. + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/operations/delete b/gcloud/alpha/number-registry/operations/delete new file mode 100644 index 000000000..7fdbf2a7e --- /dev/null +++ b/gcloud/alpha/number-registry/operations/delete @@ -0,0 +1,64 @@ +NAME + gcloud alpha number-registry operations delete - delete operations + +SYNOPSIS + gcloud alpha number-registry operations delete + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an operation + +EXAMPLES + To delete the operation, run: + + $ gcloud alpha number-registry operations delete + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to be deleted. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/operations/describe b/gcloud/alpha/number-registry/operations/describe new file mode 100644 index 000000000..f7f995b36 --- /dev/null +++ b/gcloud/alpha/number-registry/operations/describe @@ -0,0 +1,64 @@ +NAME + gcloud alpha number-registry operations describe - describe operations + +SYNOPSIS + gcloud alpha number-registry operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an operation + +EXAMPLES + To describe the operation, run: + + $ gcloud alpha number-registry operations describe + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation 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: + ◆ 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/operations/help b/gcloud/alpha/number-registry/operations/help new file mode 100644 index 000000000..8a5ebe8dd --- /dev/null +++ b/gcloud/alpha/number-registry/operations/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha number-registry operations - manage Operation resources + +SYNOPSIS + gcloud alpha number-registry operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Operation resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel operations. + + delete + (ALPHA) Delete operations. + + describe + (ALPHA) Describe operations. + + list + (ALPHA) List operations. + + wait + (ALPHA) Wait operations. + +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. + diff --git a/gcloud/alpha/number-registry/operations/list b/gcloud/alpha/number-registry/operations/list new file mode 100644 index 000000000..63573ac0b --- /dev/null +++ b/gcloud/alpha/number-registry/operations/list @@ -0,0 +1,85 @@ +NAME + gcloud alpha number-registry operations list - list operations + +SYNOPSIS + gcloud alpha number-registry operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List operations + +EXAMPLES + To list all operations, run: + + $ gcloud alpha number-registry operations list + +REQUIRED FLAGS + Location resource - The name of the operation's parent resource. 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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/operations/wait b/gcloud/alpha/number-registry/operations/wait new file mode 100644 index 000000000..85e22925d --- /dev/null +++ b/gcloud/alpha/number-registry/operations/wait @@ -0,0 +1,64 @@ +NAME + gcloud alpha number-registry operations wait - wait operations + +SYNOPSIS + gcloud alpha number-registry operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Wait an operation + +EXAMPLES + To wait the operation, run: + + $ gcloud alpha number-registry operations wait + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to wait on. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/create b/gcloud/alpha/number-registry/registry-books/create new file mode 100644 index 000000000..de127245f --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/create @@ -0,0 +1,96 @@ +NAME + gcloud alpha number-registry registry-books create - create a registry book + resource + +SYNOPSIS + gcloud alpha number-registry registry-books create + (REGISTRY_BOOK : --location=LOCATION) [--async] [--labels=[LABELS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a registry book resource. + +EXAMPLES + To create an registry book my-registry-book in location global run: + + $ gcloud alpha number-registry registry-books create \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook resource - Identifier. name of 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: + ◆ provide the argument registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_book 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. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/delete b/gcloud/alpha/number-registry/registry-books/delete new file mode 100644 index 000000000..531d80252 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/delete @@ -0,0 +1,88 @@ +NAME + gcloud alpha number-registry registry-books delete - delete a single + registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books delete + (REGISTRY_BOOK : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single registry book. + +EXAMPLES + To delete a registry book my-registry-book in location global run: + + $ gcloud alpha number-registry registry-books delete \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook resource - Name of the 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: + ◆ provide the argument registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_book 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. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/describe b/gcloud/alpha/number-registry/registry-books/describe new file mode 100644 index 000000000..425ebf636 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry registry-books describe - gets details of a + single registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books describe + (REGISTRY_BOOK : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single registry book resource. + +EXAMPLES + To get the details of a single registry book my-registry-book in location + global run: + + $ gcloud alpha number-registry registry-books describe \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook resource - Name of the 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: + ◆ provide the argument registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_book 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/help b/gcloud/alpha/number-registry/registry-books/help new file mode 100644 index 000000000..82bfd844c --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/help @@ -0,0 +1,52 @@ +NAME + gcloud alpha number-registry registry-books - manage registry book + resources + +SYNOPSIS + gcloud alpha number-registry registry-books GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage registry book resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + historical-events + (ALPHA) Manage historical event resources. + + node-events + (ALPHA) Manage node event resources. + + registry-nodes + (ALPHA) Manage registry node resources. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a registry book resource. + + delete + (ALPHA) Delete a single registry book resource. + + describe + (ALPHA) Gets details of a single registry book resource. + + list + (ALPHA) List registry book resources. + + update + (ALPHA) Update the parameters of a single registry book resource. + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/historical-events/help b/gcloud/alpha/number-registry/registry-books/historical-events/help new file mode 100644 index 000000000..5dfce1bd9 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/historical-events/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha number-registry registry-books historical-events - manage + historical event resources + +SYNOPSIS + gcloud alpha number-registry registry-books historical-events COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage historical event resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + show + (ALPHA) List all historical events in a registry book. + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/historical-events/show b/gcloud/alpha/number-registry/registry-books/historical-events/show new file mode 100644 index 000000000..bfa1ca5f7 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/historical-events/show @@ -0,0 +1,95 @@ +NAME + gcloud alpha number-registry registry-books historical-events show - list + all historical events in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books historical-events show + (--registry-book=REGISTRY_BOOK : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all historical events in a registry book. + +EXAMPLES + To list all historical events in registry book my-registry-book in location + global run: + + $ gcloud alpha number-registry registry-books historical-events \ show --registry-book=my-registry-book --location=global + +REQUIRED FLAGS + RegistryBook resource - Parent value for ShowHistoricalEventsRequest 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 --registry-book 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. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ▸ provide the argument --registry-book on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument --registry-book on the command line with a + fully specified name; + ▸ 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/list b/gcloud/alpha/number-registry/registry-books/list new file mode 100644 index 000000000..c59973696 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha number-registry registry-books list - list registry book + resources + +SYNOPSIS + gcloud alpha number-registry registry-books list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List registry book resources. + +EXAMPLES + To list all registry books in location global run: + + $ gcloud alpha number-registry registry-books list --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListRegistryBooksRequest 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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/node-events/help b/gcloud/alpha/number-registry/registry-books/node-events/help new file mode 100644 index 000000000..f95c07d46 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/node-events/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha number-registry registry-books node-events - manage node event + resources + +SYNOPSIS + gcloud alpha number-registry registry-books node-events COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage node event resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + show + (ALPHA) List all node events of an IP range in a registry book. + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/node-events/show b/gcloud/alpha/number-registry/registry-books/node-events/show new file mode 100644 index 000000000..fdfff691b --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/node-events/show @@ -0,0 +1,101 @@ +NAME + gcloud alpha number-registry registry-books node-events show - list all + node events of an IP range in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books node-events show + --ip-range=IP_RANGE + (--registry-book=REGISTRY_BOOK : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all node events of an IP range in a registry book. + +EXAMPLES + To list all node events of IP range 10.10.20.0/24 in registry book + my-registry-book in location global run: + + $ gcloud alpha number-registry registry-books node-events show \ + --ip-range=10.10.20.0/24 --registry-book=my-registry-book \ + --location=global + +REQUIRED FLAGS + --ip-range=IP_RANGE + The IP range of node events to list. + + RegistryBook resource - Parent value for ShowNodeEventsRequest 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 --registry-book 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. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ▸ provide the argument --registry-book on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument --registry-book on the command line with a + fully specified name; + ▸ 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/create b/gcloud/alpha/number-registry/registry-books/registry-nodes/create new file mode 100644 index 000000000..73a382d05 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/create @@ -0,0 +1,155 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes create - create + a registry node resource in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes create + (REGISTRY_NODE : --location=LOCATION --registry-book=REGISTRY_BOOK) + --ip-range=IP_RANGE [--async] + [--attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE]] + [--labels=[LABELS,...]] + [--import-info-source=IMPORT_INFO_SOURCE + --import-info-writer=IMPORT_INFO_WRITER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a registry node resource in a registry book. + +EXAMPLES + To create a registry node my-registry-node under registry book + my-registry-book with IP range 10.10.10.0/24 in location global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ create my-registry-node --registry-book=my-registry-book \ + --ip-range=10.10.10.0/24 --location=global + + To create a registry node my-registry-node under registry book + my-registry-book with IP range 10.10.20.0/24 with two attributes in + location global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ create my-registry-node --registry-book=my-registry-book \ + --ip-range=10.10.20.0/24 \ + --attribute=key='gke',value='gke usage' \ + --attribute=key='gce subnet',value='gce subnet for auto gke' \ + --location=global + +POSITIONAL ARGUMENTS + RegistryNode resource - Identifier. name of 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: + ◆ provide the argument registry_node 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. + + REGISTRY_NODE + ID of the registryNode or fully qualified identifier for the + registryNode. + + To set the registry_node attribute: + ▸ provide the argument registry_node on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --registry-book=REGISTRY_BOOK + registryBooks TBD + + To set the registry-book attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --registry-book on the command line. + +REQUIRED FLAGS + --ip-range=IP_RANGE + IP range of registry node. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + Attributes represent the custom metadata for registry node. + + description + The description of the registry node attribute. + + key + The key of the registry attribute. + + value + The value of the registry node attribute. + + Shorthand Example: + + --attribute=description=string,key=string,value=string --attribute=description=string,key=string,value=string + + JSON Example: + + --attribute='[{"description": "string", "key": "string", "value": "string"}]' + + File Example: + + --attribute=path_to_file.(yaml|json) + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + Message describing import metadata. + + --import-info-source=IMPORT_INFO_SOURCE + Resource name of imported source. + + --import-info-writer=IMPORT_INFO_WRITER + Writer of imported information. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/delete b/gcloud/alpha/number-registry/registry-books/registry-nodes/delete new file mode 100644 index 000000000..c9e05cd0f --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/delete @@ -0,0 +1,97 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes delete - delete + a single registry node from a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes delete + (REGISTRY_NODE : --location=LOCATION --registry-book=REGISTRY_BOOK) + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single registry node from a registry book. + +EXAMPLES + To delete a registry node my-registry-node from registry book + my-registry-book run: + + $ gcloud alpha number-registry registry-books registry-nodes \ delete my-registry-node --registry-book=my-registry-book \ + --location=global + +POSITIONAL ARGUMENTS + RegistryNode resource - Name of the 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: + ◆ provide the argument registry_node 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. + + REGISTRY_NODE + ID of the registryNode or fully qualified identifier for the + registryNode. + + To set the registry_node attribute: + ▸ provide the argument registry_node on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --registry-book=REGISTRY_BOOK + registryBooks TBD + + To set the registry-book attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --registry-book on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/describe b/gcloud/alpha/number-registry/registry-books/registry-nodes/describe new file mode 100644 index 000000000..41d5b0073 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/describe @@ -0,0 +1,77 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes describe - gets + details of a single registry node resource + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes describe + (REGISTRY_NODE : --location=LOCATION --registry-book=REGISTRY_BOOK) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single registry node resource. + +EXAMPLES + To get the details of a single registry node my-registry-node in location + global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ describe my-registry-node --registry-book=my-registry-book \ + --location=global + +POSITIONAL ARGUMENTS + RegistryNode resource - Name of the 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: + ◆ provide the argument registry_node 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. + + REGISTRY_NODE + ID of the registryNode or fully qualified identifier for the + registryNode. + + To set the registry_node attribute: + ▸ provide the argument registry_node on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --registry-book=REGISTRY_BOOK + registryBooks TBD + + To set the registry-book attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --registry-book 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/help b/gcloud/alpha/number-registry/registry-books/registry-nodes/help new file mode 100644 index 000000000..ac1389a3f --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes - manage + registry node resources + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage registry node resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a registry node resource in a registry book. + + delete + (ALPHA) Delete a single registry node from a registry book. + + describe + (ALPHA) Gets details of a single registry node resource. + + list + (ALPHA) List registry node resources in a registry book. + + search + (ALPHA) Search registry node resources in a registry book. + + update + (ALPHA) Update the parameters of a single registry node resource. + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/list b/gcloud/alpha/number-registry/registry-books/registry-nodes/list new file mode 100644 index 000000000..a9e1693b7 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/list @@ -0,0 +1,102 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes list - list + registry node resources in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes list + (--registry-book=REGISTRY_BOOK : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List registry node resources in a registry book. + +EXAMPLES + To list all registry nodes in registry book my-registry-book in location + global run: + + $ gcloud alpha number-registry registry-books registry-nodes list \ + --registry-book=my-registry-book --location=global + +REQUIRED FLAGS + RegistryBook resource - Parent value for ListRegistryNodesRequest 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 --registry-book 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. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ▸ provide the argument --registry-book on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument --registry-book on the command line with a + fully specified name; + ▸ 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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/search b/gcloud/alpha/number-registry/registry-books/registry-nodes/search new file mode 100644 index 000000000..3cf4b52ad --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/search @@ -0,0 +1,118 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes search - search + registry node resources in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes search + (--registry-book=REGISTRY_BOOK : --location=LOCATION) + [--attribute-keys=[ATTRIBUTE_KEYS,...]] [--ip-range=IP_RANGE] + [--keywords=[KEYWORDS,...]] [--source=SOURCE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Search registry node resources in a registry book. + +EXAMPLES + To search all registry nodes containing keyword gke in registry book + my-registry-book in location global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ search --keywords='gke' --registry-book=my-registry-book \ + --location=global + + To search all registry nodes with IP range 192.168.0.0/24 in registry book + my-registry-book in location global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ search --ip-range='192.168.0.0/24' \ + --registry-book=my-registry-book --location=global + +REQUIRED FLAGS + RegistryBook resource - Name of the parent 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: + ◆ provide the argument --registry-book 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. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ▸ provide the argument --registry-book on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument --registry-book on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --attribute-keys=[ATTRIBUTE_KEYS,...] + A list of attribute keys owned by the registry nodes. + + --ip-range=IP_RANGE + IP range to filter for registry node. + + --keywords=[KEYWORDS,...] + A list of keywords that are contained by the attribute values within + registry nodes. + + --source=SOURCE + Source filter of the registry nodes. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/registry-nodes/update b/gcloud/alpha/number-registry/registry-books/registry-nodes/update new file mode 100644 index 000000000..94463aa7a --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/registry-nodes/update @@ -0,0 +1,245 @@ +NAME + gcloud alpha number-registry registry-books registry-nodes update - update + the parameters of a single registry node resource + +SYNOPSIS + gcloud alpha number-registry registry-books registry-nodes update + (REGISTRY_NODE : --location=LOCATION --registry-book=REGISTRY_BOOK) + [--async] [--ip-range=IP_RANGE] + [--attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + | --add-attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + --clear-attribute + | --remove-attribute=[description=DESCRIPTION], + [key=KEY],[value=VALUE]] + [--import-info-source=IMPORT_INFO_SOURCE + --import-info-writer=IMPORT_INFO_WRITER] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the parameters of a single registry node resource. + +EXAMPLES + To update the IP range of a registry node my-registry-node with a new IP + range 10.20.10.0/24 in location global run: + + $ gcloud alpha number-registry registry-books registry-nodes \ update my-registry-node --ip-range=10.20.10.0/24 \ + --location=global --registry-book=my-registry-book + +POSITIONAL ARGUMENTS + RegistryNode resource - Identifier. name of 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: + ◆ provide the argument registry_node 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. + + REGISTRY_NODE + ID of the registryNode or fully qualified identifier for the + registryNode. + + To set the registry_node attribute: + ▸ provide the argument registry_node on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --registry-book=REGISTRY_BOOK + registryBooks TBD + + To set the registry-book attribute: + ▸ provide the argument registry_node on the command line with a + fully specified name; + ▸ provide the argument --registry-book on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ip-range=IP_RANGE + IP range of registry node. + + Update attribute. + + At most one of these can be specified: + + --attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + Set attribute to new value. Attributes represent the custom metadata + for registry node. + + description + The description of the registry node attribute. + + key + The key of the registry attribute. + + value + The value of the registry node attribute. + + Shorthand Example: + + --attribute=description=string,key=string,value=string --attribute=description=string,key=string,value=string + + JSON Example: + + --attribute='[{"description": "string", "key": "string", "value": "string"}]' + + File Example: + + --attribute=path_to_file.(yaml|json) + + --add-attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + Add new value to attribute list. Attributes represent the custom + metadata for registry node. + + description + The description of the registry node attribute. + + key + The key of the registry attribute. + + value + The value of the registry node attribute. + + Shorthand Example: + + --add-attribute=description=string,key=string,value=string --add-attribute=description=string,key=string,value=string + + JSON Example: + + --add-attribute='[{"description": "string", "key": "string", "value": "string"}]' + + File Example: + + --add-attribute=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-attribute + Clear attribute value and set to empty list. + + --remove-attribute=[description=DESCRIPTION],[key=KEY],[value=VALUE] + Remove existing value from attribute list. Attributes represent the + custom metadata for registry node. + + description + The description of the registry node attribute. + + key + The key of the registry attribute. + + value + The value of the registry node attribute. + + Shorthand Example: + + --remove-attribute=description=string,key=string,value=string --remove-attribute=description=string,key=string,value=string + + JSON Example: + + --remove-attribute='[{"description": "string", "key": "string", "value": "string"}]' + + File Example: + + --remove-attribute=path_to_file.(yaml|json) + + Message describing import metadata. + + --import-info-source=IMPORT_INFO_SOURCE + Resource name of imported source. + + --import-info-writer=IMPORT_INFO_WRITER + Writer of imported information. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/number-registry/registry-books/update b/gcloud/alpha/number-registry/registry-books/update new file mode 100644 index 000000000..102e0ffc1 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/update @@ -0,0 +1,135 @@ +NAME + gcloud alpha number-registry registry-books update - update the parameters + of a single registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books update + (REGISTRY_BOOK : --location=LOCATION) [--async] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a registry book resource. + +EXAMPLES + To update the name of a registry book my-registry-book in location global + run: + + $ gcloud alpha number-registry registry-books update \ + my-registry-book --location=global \ + --name="updated-registry-book" + +POSITIONAL ARGUMENTS + RegistryBook resource - Identifier. name of 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: + ◆ provide the argument registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument registry_book 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. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: http://go/cloud-number-registry + +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. + diff --git a/gcloud/alpha/scc/findings/group b/gcloud/alpha/scc/findings/group index 57233cb73..650090922 100644 --- a/gcloud/alpha/scc/findings/group +++ b/gcloud/alpha/scc/findings/group @@ -41,20 +41,6 @@ EXAMPLES $ gcloud alpha scc findings group 123456 --source=5678 \ --group-by="category" --filter="state=\"ACTIVE\"" - Group ACTIVE findings under organization 123456 and source 5678, on - 2019-01-01T01:00:00 GMT, by their category: - - $ gcloud alpha scc findings group 123456 --source=5678 \ - --group-by="category" \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" - - Group findings under organization 123456 and source 5678 into following 3 - state_changes (ADDED/CHANGED/UNCHANGED) based on the activity during past - 24 hours: - - $ gcloud alpha scc findings group 123456 --source=5678 \ - --group-by="state_change" --compare-duration=86400s - Group findings under organization 123456 and location=eu across all sources by their category: @@ -77,16 +63,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -100,11 +87,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --filter=FILTER Expression that defines the filter to apply across findings. The @@ -156,9 +148,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/alpha/scc/findings/list b/gcloud/alpha/scc/findings/list index 5d0f9b94a..aa5f609c4 100644 --- a/gcloud/alpha/scc/findings/list +++ b/gcloud/alpha/scc/findings/list @@ -57,13 +57,7 @@ EXAMPLES under organization 123456: $ gcloud alpha scc findings list 123456 --filter="state=\"ACTIVE\" \ - AND event_time > 1546304400000" - - List all findings that were ACTIVE as of 2019-01-01T01:00:00 GMT time, - under organization 123456: - - $ gcloud alpha scc findings list 123456 \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + AND event_time > 1546304400000"" List all findings under organization 123456 across all sources and location=eu: @@ -86,16 +80,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -109,11 +104,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --field-mask=FIELD_MASK Field mask to specify the finding fields listed in the response. An @@ -152,9 +152,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/alpha/scc/findings/list-marks b/gcloud/alpha/scc/findings/list-marks index 6c17f001a..686253bf7 100644 --- a/gcloud/alpha/scc/findings/list-marks +++ b/gcloud/alpha/scc/findings/list-marks @@ -95,9 +95,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/scc/manage/help b/gcloud/alpha/scc/manage/help index 6620ca28b..b815e929d 100644 --- a/gcloud/alpha/scc/manage/help +++ b/gcloud/alpha/scc/manage/help @@ -19,6 +19,9 @@ GROUPS custom-modules (ALPHA) Manage Cloud SCC (Security Command Center) custom modules. + services + (ALPHA) Manage Cloud SCC (Security Command Center) services. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/scc/manage/services/describe b/gcloud/alpha/scc/manage/services/describe new file mode 100644 index 000000000..814104d45 --- /dev/null +++ b/gcloud/alpha/scc/manage/services/describe @@ -0,0 +1,74 @@ +NAME + gcloud alpha scc manage services describe - get the details of a Security + Command Center service + +SYNOPSIS + gcloud alpha scc manage services describe SERVICE_NAME + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the details of a Security Command Center service. It resolves + INHERITED enablement states to ENABLED or DISABLED for services at ancestor + levels. For example, if the service is enabled at the ancestor level, + services for all child resources will have the enablement state set to + ENABLED. + +EXAMPLES + To get the details of a Security Command Center service with name sha for + organization 123, run: + + $ gcloud alpha scc manage services describe sha --organization=123 + + To get the details of a Security Command Center service with name sha for + folder 456, run: + + $ gcloud alpha scc manage services describe sha --folder=456 + + To get the details of a Security Command Center service with ID sha for + project 789, run: + + $ gcloud alpha scc manage services describe sha --project=789 + + You can also specify the parent more generally: + + $ gcloud alpha scc manage services describe sha \ + --parent=organizations/123 + +POSITIONAL ARGUMENTS + SERVICE_NAME + The service name, provided either in lowercase hyphenated form (e.g. + security-health-analytics), or in abbreviated form (e.g. sha) + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the custom module. + + --organization=ORGANIZATION_ID + Organization associated with the custom module. + + --parent=PARENT + Parent associated with the custom module. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the custom module. + +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. This variant is also available: + + $ gcloud scc manage services describe + diff --git a/gcloud/alpha/scc/manage/services/help b/gcloud/alpha/scc/manage/services/help new file mode 100644 index 000000000..01b37a050 --- /dev/null +++ b/gcloud/alpha/scc/manage/services/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha scc manage services - manage Cloud SCC + (Security Command Center) services + +SYNOPSIS + gcloud alpha scc manage services COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud SCC (Security Command Center) services. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Get the details of a Security Command Center service. + + list + (ALPHA) List the details of Security Command Center services. + + update + (ALPHA) Update a Security Command Center service. + +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: + + $ gcloud scc manage services + diff --git a/gcloud/alpha/scc/manage/services/list b/gcloud/alpha/scc/manage/services/list new file mode 100644 index 000000000..0d16b9426 --- /dev/null +++ b/gcloud/alpha/scc/manage/services/list @@ -0,0 +1,92 @@ +NAME + gcloud alpha scc manage services list - list the details of Security + Command Center services + +SYNOPSIS + gcloud alpha scc manage services list + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the details of Security Command Center services for the + specified folder, project or organization. Services along with their + corresponding module information is returned as the response. + +EXAMPLES + To list the Security Center services for organization 123, run: + + $ gcloud alpha scc manage services list \ + --organization=organizations/123 + + To list Security Center services for folder 456, run: + + $ gcloud alpha scc manage services list --folder=folders/456 + + To list Security Center services for project 789, run: + + $ gcloud alpha scc manage services list --project=projects/789 + + You can also specify the parent more generally: + + $ gcloud alpha scc manage services list --parent=organizations/123 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the Security Center service. + + --organization=ORGANIZATION_ID + Organization associated with the Security Center service. + + --parent=PARENT + Parent associated with the Security Center service. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the Security Center service. + +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. This variant is also available: + + $ gcloud scc manage services list + diff --git a/gcloud/alpha/scc/manage/services/update b/gcloud/alpha/scc/manage/services/update new file mode 100644 index 000000000..772ebc0ae --- /dev/null +++ b/gcloud/alpha/scc/manage/services/update @@ -0,0 +1,91 @@ +NAME + gcloud alpha scc manage services update - update a Security Command Center + service + +SYNOPSIS + gcloud alpha scc manage services update SERVICE_NAME + (--enablement-state=ENABLEMENT_STATE + --module-config-file=MODULE_CONFIG_FILE) + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the enablement state of the Security Center service and its + corresponding modules for the specified folder, project or organization. + +EXAMPLES + To update a Security Center Service with name sha for organization 123, + run: + + $ gcloud alpha scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" + + To update a Security Center Service with name sha and its modules for + organization 123, run: + + $ gcloud alpha scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" \ + --module-config-file=module_config.yaml + + To validate an update of Security Center Service with name sha and its + modules for organization 123, run: + + $ gcloud alpha scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" \ + --module-config-file=module_config.yaml --validate-only + +POSITIONAL ARGUMENTS + SERVICE_NAME + The service name, provided either in lowercase hyphenated form (e.g. + security-health-analytics), or in abbreviated form (e.g. sha) + +REQUIRED FLAGS + At least one of these must be specified: + + --enablement-state=ENABLEMENT_STATE + Sets the enablement state of the Security Center service. Valid + options are ENABLED, DISABLED, OR INHERITED. The INHERITED state is + only valid when setting the enablement state at the project or folder + level. + + --module-config-file=MODULE_CONFIG_FILE + Path to a JSON or YAML file that contains the module config to set + for the given module and service. + + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the custom module. + + --organization=ORGANIZATION_ID + Organization associated with the custom module. + + --parent=PARENT + Parent associated with the custom module. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the custom module. + +OPTIONAL FLAGS + --validate-only + If present, the request is validated (including IAM checks) but no + action is taken. + +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. This variant is also available: + + $ gcloud scc manage services update + diff --git a/gcloud/app/deploy b/gcloud/app/deploy index f70fef36c..b7a6c3187 100644 --- a/gcloud/app/deploy +++ b/gcloud/app/deploy @@ -15,17 +15,16 @@ DESCRIPTION uploaded. A DEPLOYABLE can be a service's .yaml file or a configuration's .yaml file (for more information about configuration files specific to your App Engine environment, refer to - https://cloud.google.com/appengine/docs/standard/python/configuration-files - or - https://cloud.google.com/appengine/docs/flexible/python/configuration-files). - Note, for Java8 Standard apps or Java11/17 Standard apps using bundled + https://cloud.google.com/appengine/docs/standard/configuration-files or + https://cloud.google.com/appengine/docs/flexible/configuration-files). + Note, for Java 8 Standard apps or Java 11/17/21 Standard apps using bundled services, you must add the path to the appengine-web.xml file inside the WEB-INF directory. gcloud app deploy skips files specified in the .gcloudignore file (see gcloud topic gcloudignore for more information). - For Java11 Standard, you can either use the yaml file, a Maven pom.xml, or + For Java 11 Standard, you can either use the yaml file, a Maven pom.xml, or a Gradle build.gradle. Alternatively, if the application is a single self-contained jar, you can give the path to the jar and a simple service - configuration will be generated. You can deploy Java11 Maven source + configuration will be generated. You can deploy Java 11 Maven source projects by specifying the location of your project's pom.xml file, and it will be built and deployed using App Engine Buildpacks. diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index c3e29cd2d..1da6ca5c8 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -129,7 +129,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/beta/alloydb/instances/create-secondary b/gcloud/beta/alloydb/instances/create-secondary index 872c5e2b8..2d65fb370 100644 --- a/gcloud/beta/alloydb/instances/create-secondary +++ b/gcloud/beta/alloydb/instances/create-secondary @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta alloydb instances create-secondary INSTANCE --cluster=CLUSTER - --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] + --region=REGION [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] + [--async] [--availability-type=AVAILABILITY_TYPE] + [--[no-]require-connectors] [--ssl-mode=SSL_MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,6 +31,16 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP + Specify to enable or disable public IP on an instance. On instance + creation only disabling public IP is allowed. If you want to enable + public IP, an instance must be created with public IP disabled first, + then update the instance to enable public IP. ASSIGN_INBOUND_PUBLIC_IP + must be (only one value is supported): + + NO_PUBLIC_IP + This disables public IP on the instance. + --async Return immediately, without waiting for the operation in progress to complete. @@ -45,6 +57,21 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --[no-]require-connectors + Enable or disable enforcing connectors only (ex: AuthProxy) connections + to the database. Use --require-connectors to enable and + --no-require-connectors to disable. + + --ssl-mode=SSL_MODE + Specify the SSL mode to use when the instance connects to the database. + Default SSL mode will match what is set on the primary instance. + SSL_MODE must be one of: + + ALLOW_UNENCRYPTED_AND_ENCRYPTED + SSL connections are optional. CA verification is not enforced. + ENCRYPTED_ONLY + SSL connections are required. CA verification is not enforced. + 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/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index 25e8068a0..deb4de29d 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -118,7 +118,7 @@ OPTIONAL FLAGS Read capacity, i.e. number of nodes in a read pool instance. --[no-]require-connectors - Enable or disable enforcing connectors only (ex: AuthProxy)connections + Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable. diff --git a/gcloud/beta/app/deploy b/gcloud/beta/app/deploy index 578a8f97d..ecb17e649 100644 --- a/gcloud/beta/app/deploy +++ b/gcloud/beta/app/deploy @@ -15,17 +15,16 @@ DESCRIPTION be uploaded. A DEPLOYABLE can be a service's .yaml file or a configuration's .yaml file (for more information about configuration files specific to your App Engine environment, refer to - https://cloud.google.com/appengine/docs/standard/python/configuration-files - or - https://cloud.google.com/appengine/docs/flexible/python/configuration-files). - Note, for Java8 Standard apps or Java11/17 Standard apps using bundled + https://cloud.google.com/appengine/docs/standard/configuration-files or + https://cloud.google.com/appengine/docs/flexible/configuration-files). + Note, for Java 8 Standard apps or Java 11/17/21 Standard apps using bundled services, you must add the path to the appengine-web.xml file inside the - WEB-INF directory. gcloud beta app deploy skips files specified in the + WEB-INF directory. gcloud app deploy skips files specified in the .gcloudignore file (see gcloud topic gcloudignore for more information). - For Java11 Standard, you can either use the yaml file, a Maven pom.xml, or + For Java 11 Standard, you can either use the yaml file, a Maven pom.xml, or a Gradle build.gradle. Alternatively, if the application is a single self-contained jar, you can give the path to the jar and a simple service - configuration will be generated. You can deploy Java11 Maven source + configuration will be generated. You can deploy Java 11 Maven source projects by specifying the location of your project's pom.xml file, and it will be built and deployed using App Engine Buildpacks. diff --git a/gcloud/beta/compute/firewall-rules/migrate b/gcloud/beta/compute/firewall-rules/migrate index a1f3f6b8f..7ce56ac3d 100644 --- a/gcloud/beta/compute/firewall-rules/migrate +++ b/gcloud/beta/compute/firewall-rules/migrate @@ -4,9 +4,13 @@ NAME SYNOPSIS gcloud beta compute firewall-rules migrate --source-network=SOURCE_NETWORK - (--bind-tags-to-instances | --export-tag-mapping + (--bind-tags-to-instances | --export-exclusion-patterns + | --export-tag-mapping | --target-firewall-policy=TARGET_FIREWALL_POLICY) - [--export-terraform-script] [--tag-mapping-file=TAG_MAPPING_FILE] + [--exclusion-patterns-file=EXCLUSION_PATTERNS_FILE] + [--export-terraform-script] [--force] + [--tag-mapping-file=TAG_MAPPING_FILE] + [--terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -32,6 +36,10 @@ REQUIRED FLAGS If set, migration tool will bind secure tags to the instances with the network tags which match secure tags from the tag mapping file. + --export-exclusion-patterns + If set, migration tool will dump list of regexes used to filter VPC + Firewall out of migration. + --export-tag-mapping If set, migration tool will inspect all VPC Firewalls attached to SOURCE_NETWORK, collect all source and target tags, and store them in @@ -42,14 +50,26 @@ REQUIRED FLAGS result. OPTIONAL FLAGS + --exclusion-patterns-file=EXCLUSION_PATTERNS_FILE + Path to a file with exclusion patterns used for VPC Firewall filtering. + Each regular expression describing a single firewall naming pattern + must be placed in a single line. No leading or tailing whitespaces. + --export-terraform-script If set, migration tool will output a terraform script to create a Firewall Policy with migrated rules. + --force + If set, migration will succeed even if the tool detects that original + rule evaluation order cannot be preserved. + --tag-mapping-file=TAG_MAPPING_FILE Path to a JSON file with legacy tags and service accounts to secure tags mapping. + --terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE + Path to a file where to store generated Terraform script. + 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/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 77fc7c0a1..2e4ed8f7c 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -619,9 +619,9 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag can be repeated to specify multiple network interfaces. The following keys are allowed: @@ -674,6 +674,30 @@ FLAGS instance network interface IPv6 access config. IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index e59ad1485..7cdca22b9 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -28,6 +28,8 @@ SYNOPSIS [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] @@ -45,7 +47,10 @@ SYNOPSIS [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE - | --image-family=IMAGE_FAMILY] [--scopes=[SCOPE,...] | --no-scopes] + | --image-family=IMAGE_FAMILY] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] + [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -417,6 +422,19 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to the instance that + is created. The address must be the first IP address in the range or + from a /96 IP address range. This option can be used only when creating + a single instance. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range. It should be used together with --internal-ipv6-address. + Only /96 IP address range is supported and the default value is 96. If + not set, either the prefix length from --internal-ipv6-address will be + used or the default value of 96 will be assigned. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -525,8 +543,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -562,6 +583,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -766,6 +820,32 @@ FLAGS By default, debian-11 is assumed for this flag. + Specifies the reservation for instances created from this template. + + --reservation=RESERVATION + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for instances created from this template. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 2166099f1..1c0b6addc 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -671,9 +671,9 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag can be repeated to specify multiple network interfaces. The following keys are allowed: @@ -726,6 +726,30 @@ FLAGS instance network interface IPv6 access config. IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, @@ -875,8 +899,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --source-machine-image=SOURCE_MACHINE_IMAGE The name of the machine image that the instance will be created from. diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 9b00db9c9..d17be6ded 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -31,6 +31,8 @@ SYNOPSIS [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] @@ -57,6 +59,8 @@ SYNOPSIS [--image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY] [--public-ptr | --no-public-ptr] [--public-ptr-domain=PUBLIC_PTR_DOMAIN | --no-public-ptr-domain] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -456,6 +460,19 @@ FLAGS Default only for Spot VMs. Stop the VM without preserving memory. The VM can be restarted later. + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to the instance that + is created. The address must be the first IP address in the range or + from a /96 IP address range. This option can be used only when creating + a single instance. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range. It should be used together with --internal-ipv6-address. + Only /96 IP address range is supported and the default value is 96. If + not set, either the prefix length from --internal-ipv6-address will be + used or the default value of 96 will be assigned. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -570,8 +587,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -607,6 +627,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -711,8 +764,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --stack-type=STACK_TYPE Specifies whether IPv6 is enabled on the default network interface. If @@ -913,6 +965,32 @@ FLAGS record for the external IP of the instance with the PTR domain name being the DNS name of the instance. + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for the instance. RESERVATION_AFFINITY must + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/beta/compute/instances/help b/gcloud/beta/compute/instances/help index def998a3a..f14bcebfc 100644 --- a/gcloud/beta/compute/instances/help +++ b/gcloud/beta/compute/instances/help @@ -113,8 +113,8 @@ COMMANDS (BETA) List Compute Engine instances. move - (BETA) Move an instance and its attached persistent disks between - zones. + (BETA) (DEPRECATED) Move an instance and its attached persistent disks + between zones. patch-partner-metadata (BETA) Patch partner metadata. diff --git a/gcloud/beta/compute/instances/move b/gcloud/beta/compute/instances/move index 11b99ee82..4f1ae9bce 100644 --- a/gcloud/beta/compute/instances/move +++ b/gcloud/beta/compute/instances/move @@ -8,10 +8,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute instances move moves a Compute Engine virtual - machine from one zone to another. Moving a virtual machine might incur - downtime if the guest OS must be shut down in order to quiesce disk volumes - prior to snapshotting. + (BETA) (DEPRECATED) This command is deprecated. Please see + https://cloud.google.com/compute/docs/instances/moving-instance-across-zones + for an alternative method. + + gcloud beta compute instances move moves a Compute Engine virtual machine + from one zone to another. Moving a virtual machine might incur downtime if + the guest OS must be shut down in order to quiesce disk volumes prior to + snapshotting. For example, running the following command moves the instance called example-instance-1 with its attached persistent disks, currently running in diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 725ab719a..93f9b1b12 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta compute public-delegated-prefixes create NAME --range=RANGE (--public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX | --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX) - [--description=DESCRIPTION] [--enable-live-migration] + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] + [--description=DESCRIPTION] [--enable-live-migration] [--mode=MODE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -36,12 +37,19 @@ REQUIRED FLAGS created from. OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + The allocatable prefix length supported by this PDP. + --description=DESCRIPTION Description of this public delegated prefix. --enable-live-migration Specify if this public delegated prefix is meant to be live migrated. + --mode=MODE + Specifies the mode of this IPv6 PDP. MODE must be one of: + EXTERNAL_IPV6_FORWARDING_RULE_CREATION, DELEGATION. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create index 2db307c6e..c6ef9fd5b 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud beta compute public-delegated-prefixes delegated-sub-prefixes create NAME --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] [--create-addresses] [--delegatee-project=DELEGATEE_PROJECT] - [--description=DESCRIPTION] [--range=RANGE] + [--description=DESCRIPTION] [--mode=MODE] [--range=RANGE] [--global-public-delegated-prefix | --public-delegated-prefix-region=PUBLIC_DELEGATED_PREFIX_REGION] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +41,9 @@ REQUIRED FLAGS for. OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + Specify allocatable prefix length supported by this sub prefix. + --create-addresses Specify if the sub prefix is delegated to create address resources in the delegatee project. Default is false. @@ -51,6 +55,10 @@ OPTIONAL FLAGS --description=DESCRIPTION Description of the delegated sub prefix to create. + --mode=MODE + Specify mode for the sub prefix. MODE must be one of: DELEGATION, + EXTERNAL_IPV6_FORWARDING_RULE_CREATION. + --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. If not specified, the entire range ofthe public diff --git a/gcloud/beta/compute/routers/add-bgp-peer b/gcloud/beta/compute/routers/add-bgp-peer index 70a1cea8d..ba6c36315 100644 --- a/gcloud/beta/compute/routers/add-bgp-peer +++ b/gcloud/beta/compute/routers/add-bgp-peer @@ -8,7 +8,9 @@ SYNOPSIS [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] - [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] + [--[no-]enable-ipv6] [--[no-]enabled] + [--export-policies=[EXPORT_POLICY,...]] + [--import-policies=[IMPORT_POLICY,...]] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] @@ -87,6 +89,14 @@ OPTIONAL FLAGS terminated and all associated routing information is removed. Enabled by default. Use --enabled to enable and --no-enabled to disable. + --export-policies=[EXPORT_POLICY,...] + Comma-separated list of export policies. Passing an empty string + removes all export policies. + + --import-policies=[IMPORT_POLICY,...] + Comma-separated list of import policies. Passing an empty string + removes all import policies. + --instance=INSTANCE Router appliance instance of the BGP peer being added. @@ -134,7 +144,7 @@ OPTIONAL FLAGS --peer-ip-address=PEER_IP_ADDRESS The address of the peer router. Must be a link-local IPv4 address in - the the range 169.254.0.0/16 or an ULA IPv6 address in the range + the range 169.254.0.0/16 or an ULA IPv6 address in the range fdff:1::/64. --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS diff --git a/gcloud/beta/compute/routers/add-route-policy b/gcloud/beta/compute/routers/add-route-policy new file mode 100644 index 000000000..bd2ca6e21 --- /dev/null +++ b/gcloud/beta/compute/routers/add-route-policy @@ -0,0 +1,63 @@ +NAME + gcloud beta compute routers add-route-policy - add an empty route policy to + a Compute Engine router + +SYNOPSIS + gcloud beta compute routers add-route-policy NAME --policy-name=POLICY_NAME + --policy-type=POLICY_TYPE [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers add-route-policy adds an empty route + policy to a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to update. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to add. + + --policy-type=POLICY_TYPE + Type of the route policy to add. POLICY_TYPE must be one of: + + EXPORT + The route policy is an export policy. + IMPORT + The route policy is an import policy. + +OPTIONAL FLAGS + --region=REGION + Region of the router to update. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This + variant is also available: + + $ gcloud alpha compute routers add-route-policy + diff --git a/gcloud/beta/compute/routers/download-route-policy b/gcloud/beta/compute/routers/download-route-policy new file mode 100644 index 000000000..ea3bdcc80 --- /dev/null +++ b/gcloud/beta/compute/routers/download-route-policy @@ -0,0 +1,63 @@ +NAME + gcloud beta compute routers download-route-policy - download a route policy + from a Compute Engine router + +SYNOPSIS + gcloud beta compute routers download-route-policy NAME + --file-name=FILE_NAME --policy-name=POLICY_NAME + [--file-format=FILE_FORMAT] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers download-route-policy downloads a route + policy from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to export. + +REQUIRED FLAGS + --file-name=FILE_NAME + The name of the file to download the route policy config to. + + --policy-name=POLICY_NAME + Name of the route policy to download. + +OPTIONAL FLAGS + --file-format=FILE_FORMAT + Format of the file passed to --file-name. FILE_FORMAT must be one of: + json, yaml. + + --region=REGION + Region of the router to export. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This + variant is also available: + + $ gcloud alpha compute routers download-route-policy + diff --git a/gcloud/beta/compute/routers/get-route-policy b/gcloud/beta/compute/routers/get-route-policy new file mode 100644 index 000000000..720a37102 --- /dev/null +++ b/gcloud/beta/compute/routers/get-route-policy @@ -0,0 +1,55 @@ +NAME + gcloud beta compute routers get-route-policy - get a route policy from a + Compute Engine router + +SYNOPSIS + gcloud beta compute routers get-route-policy NAME --policy-name=POLICY_NAME + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers get-route-policy gets a route policy + from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to get. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to get. + +OPTIONAL FLAGS + --region=REGION + Region of the router to get. If not specified, you might be prompted to + select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This + variant is also available: + + $ gcloud alpha compute routers get-route-policy + diff --git a/gcloud/beta/compute/routers/help b/gcloud/beta/compute/routers/help index 73ce37d41..1ad0f8ef5 100644 --- a/gcloud/beta/compute/routers/help +++ b/gcloud/beta/compute/routers/help @@ -35,6 +35,9 @@ COMMANDS add-interface (BETA) Add an interface to a Compute Engine router. + add-route-policy + (BETA) Add an empty route policy to a Compute Engine router. + create (BETA) Create a Compute Engine router. @@ -44,24 +47,40 @@ COMMANDS describe (BETA) Describe a Compute Engine router. + download-route-policy + (BETA) Download a route policy from a Compute Engine router. + get-nat-ip-info (BETA) Display NAT IP information in a router. get-nat-mapping-info (BETA) Display NAT Mapping information in a router. + get-route-policy + (BETA) Get a route policy from a Compute Engine router. + get-status (BETA) Get status of a Compute Engine router. list (BETA) List Google Compute Engine routers. + list-bgp-routes + (BETA) List routes advertised and learned on individual BGP sessions, + both pre- and post-policy evaluation. + + list-route-policies + (BETA) List route policies from a Compute Engine router. + remove-bgp-peer (BETA) Remove a BGP peer from a Compute Engine router. remove-interface (BETA) Remove an interface from a Compute Engine router. + remove-route-policy + (BETA) Remove a route policy from a Compute Engine router. + update (BETA) Update a Compute Engine router. @@ -71,6 +90,9 @@ COMMANDS update-interface (BETA) Update an interface on a Compute Engine router. + upload-route-policy + (BETA) Upload a route policy into a Compute Engine router. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/compute/routers/list-bgp-routes b/gcloud/beta/compute/routers/list-bgp-routes new file mode 100644 index 000000000..959a1cbcc --- /dev/null +++ b/gcloud/beta/compute/routers/list-bgp-routes @@ -0,0 +1,118 @@ +NAME + gcloud beta compute routers list-bgp-routes - list routes advertised and + learned on individual BGP sessions, both pre- and post-policy + evaluation + +SYNOPSIS + gcloud beta compute routers list-bgp-routes NAME + --address-family=ADDRESS_FAMILY --peer=PEER + --route-direction=ROUTE_DIRECTION [--destination-range=CIDR_RANGE] + [--no-policy-applied] [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers list-bgp-routes lists routes advertised + and learned on individual BGP sessions, both pre- and post-policy + evaluation. + +POSITIONAL ARGUMENTS + NAME + Name of the router to list. + +REQUIRED FLAGS + --address-family=ADDRESS_FAMILY + Limit results to routes learned for this Address Family Identifier. + ADDRESS_FAMILY must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. + + --peer=PEER + Limit results to routes learned from this peer (name). + + --route-direction=ROUTE_DIRECTION + Limit results to routes in this direction. ROUTE_DIRECTION must be one + of: + + INBOUND + Learned routes. + OUTBOUND + Advertised routes. + +FLAGS + --destination-range=CIDR_RANGE + Limit results to prefixes. + + --policy-applied + Routes returned are post-policy evaluation. Enabled by default, use + --no-policy-applied to disable. + + --region=REGION + Region of the router to list. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. This + variant is also available: + + $ gcloud alpha compute routers list-bgp-routes + diff --git a/gcloud/beta/compute/routers/list-route-policies b/gcloud/beta/compute/routers/list-route-policies new file mode 100644 index 000000000..eb3e062d3 --- /dev/null +++ b/gcloud/beta/compute/routers/list-route-policies @@ -0,0 +1,84 @@ +NAME + gcloud beta compute routers list-route-policies - list route policies from + a Compute Engine router + +SYNOPSIS + gcloud beta compute routers list-route-policies NAME [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers list-route-policies lists all route + policies from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to list. + +FLAGS + --region=REGION + Region of the router to list. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. This + variant is also available: + + $ gcloud alpha compute routers list-route-policies + diff --git a/gcloud/beta/compute/routers/remove-route-policy b/gcloud/beta/compute/routers/remove-route-policy new file mode 100644 index 000000000..d41996b7b --- /dev/null +++ b/gcloud/beta/compute/routers/remove-route-policy @@ -0,0 +1,55 @@ +NAME + gcloud beta compute routers remove-route-policy - remove a route policy + from a Compute Engine router + +SYNOPSIS + gcloud beta compute routers remove-route-policy NAME + --policy-name=POLICY_NAME [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers remove-route-policy removes a route + policy from a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to delete. + +REQUIRED FLAGS + --policy-name=POLICY_NAME + Name of the route policy to be removed. + +OPTIONAL FLAGS + --region=REGION + Region of the router to delete. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This + variant is also available: + + $ gcloud alpha compute routers remove-route-policy + diff --git a/gcloud/beta/compute/routers/update-bgp-peer b/gcloud/beta/compute/routers/update-bgp-peer index 895cd84dd..7bb926c05 100644 --- a/gcloud/beta/compute/routers/update-bgp-peer +++ b/gcloud/beta/compute/routers/update-bgp-peer @@ -7,7 +7,9 @@ SYNOPSIS [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] - [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] + [--[no-]enable-ipv6] [--[no-]enabled] + [--export-policies=[EXPORT_POLICY,...]] + [--import-policies=[IMPORT_POLICY,...]] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] @@ -87,6 +89,14 @@ OPTIONAL FLAGS terminated and all associated routing information is removed. Use --enabled to enable and --no-enabled to disable. + --export-policies=[EXPORT_POLICY,...] + Comma-separated list of export policies. Passing an empty string + removes all export policies. + + --import-policies=[IMPORT_POLICY,...] + Comma-separated list of import policies. Passing an empty string + removes all import policies. + --interface=INTERFACE The name of the interface for this BGP peer. @@ -121,7 +131,7 @@ OPTIONAL FLAGS --peer-ip-address=PEER_IP_ADDRESS The address of the peer router. Must be a link-local IPv4 address in - the the range 169.254.0.0/16 or an ULA IPv6 address in the range + the range 169.254.0.0/16 or an ULA IPv6 address in the range fdff:1::/64. --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS diff --git a/gcloud/beta/compute/routers/upload-route-policy b/gcloud/beta/compute/routers/upload-route-policy new file mode 100644 index 000000000..61a0cf48d --- /dev/null +++ b/gcloud/beta/compute/routers/upload-route-policy @@ -0,0 +1,63 @@ +NAME + gcloud beta compute routers upload-route-policy - upload a route policy + into a Compute Engine router + +SYNOPSIS + gcloud beta compute routers upload-route-policy NAME --file-name=FILE_NAME + [--file-format=FILE_FORMAT] [--policy-name=POLICY_NAME] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute routers upload-route-policy uploads a route + policy into a Compute Engine router. + +POSITIONAL ARGUMENTS + NAME + Name of the router to upload. + +REQUIRED FLAGS + --file-name=FILE_NAME + Local path to the file defining the policy + +OPTIONAL FLAGS + --file-format=FILE_FORMAT + Format of the file passed to --file-name. FILE_FORMAT must be one of: + json, yaml. + + --policy-name=POLICY_NAME + Name of the route policy to add/replace. + + --region=REGION + Region of the router to upload. If not specified, you might be prompted + to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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. This + variant is also available: + + $ gcloud alpha compute routers upload-route-policy + diff --git a/gcloud/beta/compute/sole-tenancy/node-groups/perform-maintenance b/gcloud/beta/compute/sole-tenancy/node-groups/perform-maintenance index efc712315..a727551cd 100644 --- a/gcloud/beta/compute/sole-tenancy/node-groups/perform-maintenance +++ b/gcloud/beta/compute/sole-tenancy/node-groups/perform-maintenance @@ -60,8 +60,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 compute sole-tenancy node-groups perform-maintenance $ gcloud alpha compute sole-tenancy node-groups perform-maintenance diff --git a/gcloud/beta/container/fleet/mesh/debug/proxy-config b/gcloud/beta/container/fleet/mesh/debug/proxy-config index 16ced4cce..c38acbcd4 100644 --- a/gcloud/beta/container/fleet/mesh/debug/proxy-config +++ b/gcloud/beta/container/fleet/mesh/debug/proxy-config @@ -26,7 +26,6 @@ REQUIRED FLAGS --type=TYPE Proxy configuration type to retrieve. - all Retrieves all configuration for the Envoy in the specified pod bootstrap Retrieves bootstrap configuration for the Envoy in the specified pod clusters/cluster Retrieves cluster configuration for the Envoy in the specified pod endpoints/endpoint Retrieves endpoint configuration for the Envoy in the specified pod @@ -35,8 +34,8 @@ REQUIRED FLAGS routes/route Retrieves route configuration for the Envoy in the specified pod secrets/secret Retrieves secret configuration for the Envoy in the specified pod - TYPE must be one of: all, bootstrap, cluster, clusters, endpoint, - endpoints, listener, listeners, log, route, routes, secret, secrets. + TYPE must be one of: bootstrap, cluster, clusters, endpoint, endpoints, + listener, listeners, log, route, routes, secret, secrets. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/container/hub/mesh/debug/proxy-config b/gcloud/beta/container/hub/mesh/debug/proxy-config index 69e8dd3c6..3876f4435 100644 --- a/gcloud/beta/container/hub/mesh/debug/proxy-config +++ b/gcloud/beta/container/hub/mesh/debug/proxy-config @@ -26,7 +26,6 @@ REQUIRED FLAGS --type=TYPE Proxy configuration type to retrieve. - all Retrieves all configuration for the Envoy in the specified pod bootstrap Retrieves bootstrap configuration for the Envoy in the specified pod clusters/cluster Retrieves cluster configuration for the Envoy in the specified pod endpoints/endpoint Retrieves endpoint configuration for the Envoy in the specified pod @@ -35,8 +34,8 @@ REQUIRED FLAGS routes/route Retrieves route configuration for the Envoy in the specified pod secrets/secret Retrieves secret configuration for the Envoy in the specified pod - TYPE must be one of: all, bootstrap, cluster, clusters, endpoint, - endpoints, listener, listeners, log, route, routes, secret, secrets. + TYPE must be one of: bootstrap, cluster, clusters, endpoint, endpoints, + listener, listeners, log, route, routes, secret, secrets. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 3ebe6e6a9..3b09c81af 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -439,6 +439,12 @@ FLAGS --clear-max-instances Clears the maximum instances setting for the function. + If it's any 2nd gen function or a 1st gen HTTP function, this flag + sets maximum instances to 0, which means there is no limit to maximum + instances. If it's an event-driven 1st gen function, this flag sets + maximum instances to 3000, which is the default value for 1st gen + functions. + --max-instances=MAX_INSTANCES Sets the maximum number of instances for the function. A function execution that would exceed max-instances times out. diff --git a/gcloud/beta/kms/keys/create b/gcloud/beta/kms/keys/create index cb9df02c6..a4b083e19 100644 --- a/gcloud/beta/kms/keys/create +++ b/gcloud/beta/kms/keys/create @@ -168,19 +168,19 @@ OPTIONAL FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --destroy-scheduled-duration=DESTROY_SCHEDULED_DURATION The amount of time that versions of the key should spend in the diff --git a/gcloud/beta/kms/keys/update b/gcloud/beta/kms/keys/update index 0be566a10..e35be2d3e 100644 --- a/gcloud/beta/kms/keys/update +++ b/gcloud/beta/kms/keys/update @@ -117,19 +117,19 @@ FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --next-rotation-time=NEXT_ROTATION_TIME Next automatic rotation time of the key. See $ gcloud topic datetimes diff --git a/gcloud/beta/kms/keys/versions/import b/gcloud/beta/kms/keys/versions/import index 23d2cec91..ba0bbae71 100644 --- a/gcloud/beta/kms/keys/versions/import +++ b/gcloud/beta/kms/keys/versions/import @@ -32,7 +32,7 @@ REQUIRED FLAGS about supported algorithms, see https://cloud.google.com/kms/docs/algorithms. ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, - aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, + aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, diff --git a/gcloud/beta/logging/views/describe b/gcloud/beta/logging/views/describe index f3618d6cd..46fa7144a 100644 --- a/gcloud/beta/logging/views/describe +++ b/gcloud/beta/logging/views/describe @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Displays information about a view. + (BETA) Displays information about a log view. EXAMPLES To describe a view in a project, run: diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index 6e0f0800f..b2fb08b5e 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -7,9 +7,10 @@ SYNOPSIS (STORAGE_POOL : --location=LOCATION) --capacity=CAPACITY --network=[name=NAME],[psa-range=PSA-RANGE] --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] - [--async] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] + [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--replica-zone=REPLICA_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a Storage Pool to contain Volumes with a specified Service @@ -138,6 +139,10 @@ OPTIONAL FLAGS To set the active_directory attribute: ▸ provide the argument --active-directory on the command line. + --allow-auto-tiering=ALLOW_AUTO_TIERING + Boolean flag indicating whether Storage Pool is allowed to use + auto-tiering + --async Return immediately, without waiting for the operation in progress to complete. @@ -180,6 +185,12 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --replica-zone=REPLICA_ZONE + String indicating replica zone for the Storage Pool + + --zone=ZONE + String indicating active zone of the Storage Pool + 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/netapp/storage-pools/help b/gcloud/beta/netapp/storage-pools/help index 3a7d74ca5..d6adb5681 100644 --- a/gcloud/beta/netapp/storage-pools/help +++ b/gcloud/beta/netapp/storage-pools/help @@ -28,6 +28,9 @@ COMMANDS list (BETA) List Cloud NetApp Storage Pools. + switch + (BETA) Switch a Regional Cloud NetApp SO Storage Pool zone. + update (BETA) Update a Cloud NetApp Storage Pool. diff --git a/gcloud/beta/netapp/storage-pools/switch b/gcloud/beta/netapp/storage-pools/switch new file mode 100644 index 000000000..b19cd579c --- /dev/null +++ b/gcloud/beta/netapp/storage-pools/switch @@ -0,0 +1,75 @@ +NAME + gcloud beta netapp storage-pools switch - switch a Regional Cloud NetApp SO + Storage Pool zone + +SYNOPSIS + gcloud beta netapp storage-pools switch + (STORAGE_POOL : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Switch a Regional Cloud NetApp SO Storage Pool zone. + +EXAMPLES + The following command switches zone of a Storage Pool named NAME using the + required arguments: + + $ gcloud beta netapp storage-pools switch NAME --location=us-central1 + + To switch zone of a Storage Pool named NAME asynchronously, run the + following command: + + $ gcloud beta netapp storage-pools switch NAME \ + --location=us-central1 --async + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to switch. 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 storage_pool 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. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha netapp storage-pools switch + diff --git a/gcloud/beta/netapp/storage-pools/update b/gcloud/beta/netapp/storage-pools/update index 4ccf29f67..288e72a11 100644 --- a/gcloud/beta/netapp/storage-pools/update +++ b/gcloud/beta/netapp/storage-pools/update @@ -5,9 +5,12 @@ NAME SYNOPSIS gcloud beta netapp storage-pools update (STORAGE_POOL : --location=LOCATION) - [--active-directory=ACTIVE_DIRECTORY] [--async] [--capacity=CAPACITY] - [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--active-directory=ACTIVE_DIRECTORY] + [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--capacity=CAPACITY] [--description=DESCRIPTION] + [--replica-zone=REPLICA_ZONE] [--update-labels=[KEY=VALUE,...]] + [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Updates a Storage Pool with given arguments @@ -77,6 +80,10 @@ FLAGS To set the active_directory attribute: ▸ provide the argument --active-directory on the command line. + --allow-auto-tiering=ALLOW_AUTO_TIERING + Boolean flag indicating whether Storage Pool is allowed to use + auto-tiering + --async Return immediately, without waiting for the operation in progress to complete. @@ -88,6 +95,9 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --replica-zone=REPLICA_ZONE + String indicating replica zone for the Storage Pool + --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. @@ -97,6 +107,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --zone=ZONE + String indicating active zone of the Storage Pool + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/netapp/volumes/create b/gcloud/beta/netapp/volumes/create index f2debb04b..39fa5deb2 100644 --- a/gcloud/beta/netapp/volumes/create +++ b/gcloud/beta/netapp/volumes/create @@ -34,6 +34,7 @@ SYNOPSIS [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--source-snapshot=SOURCE_SNAPSHOT] + [--tiering-policy=[tier-action=ENABLED|PAUSED,...]] [--unix-permissions=UNIX_PERMISSIONS] [--source-backup=SOURCE_BACKUP : --backup_vault=BACKUP_VAULT] [GCLOUD_WIDE_FLAG ...] @@ -249,6 +250,18 @@ OPTIONAL FLAGS To set the snapshot attribute: ▸ provide the argument --source-snapshot on the command line. + --tiering-policy=[tier-action=ENABLED|PAUSED,...] + Tiering Policy contains auto tiering policy on a volume. + + Tiering Policy will have the following format + --tiering-policy=tier-action=TIER_ACTION, + cooling-threshold-days=COOLING_THRESHOLD_DAYS + + tier-action is an enum, supported values are ENABLED or PAUSED, + cooling-threshold-days is an integer represents time in days to mark + the volume's data block as cold and make it eligible for tiering, can + be range from 7-183. Default is 31. + --unix-permissions=UNIX_PERMISSIONS Unix permissions the mount point will be created with. Unix permissions are only applicable with NFS protocol only diff --git a/gcloud/beta/netapp/volumes/update b/gcloud/beta/netapp/volumes/update index e43eae764..de90f63e4 100644 --- a/gcloud/beta/netapp/volumes/update +++ b/gcloud/beta/netapp/volumes/update @@ -32,6 +32,7 @@ SYNOPSIS [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--source-snapshot=SOURCE_SNAPSHOT] [--storage-pool=STORAGE_POOL] + [--tiering-policy=[tier-action=ENABLED|PAUSED,...]] [--unix-permissions=UNIX_PERMISSIONS] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--source-backup=SOURCE_BACKUP : --backup_vault=BACKUP_VAULT] @@ -220,6 +221,18 @@ FLAGS To set the storage_pool attribute: ▸ provide the argument --storage-pool on the command line. + --tiering-policy=[tier-action=ENABLED|PAUSED,...] + Tiering Policy contains auto tiering policy on a volume. + + Tiering Policy will have the following format + --tiering-policy=tier-action=TIER_ACTION, + cooling-threshold-days=COOLING_THRESHOLD_DAYS + + tier-action is an enum, supported values are ENABLED or PAUSED, + cooling-threshold-days is an integer represents time in days to mark + the volume's data block as cold and make it eligible for tiering, can + be range from 7-183. Default is 31. + --unix-permissions=UNIX_PERMISSIONS Unix permissions the mount point will be created with. Unix permissions are only applicable with NFS protocol only diff --git a/gcloud/beta/scc/findings/group b/gcloud/beta/scc/findings/group index 9fb32f57b..6eeace17c 100644 --- a/gcloud/beta/scc/findings/group +++ b/gcloud/beta/scc/findings/group @@ -41,20 +41,6 @@ EXAMPLES $ gcloud beta scc findings group 123456 --source=5678 \ --group-by="category" --filter="state=\"ACTIVE\"" - Group ACTIVE findings under organization 123456 and source 5678, on - 2019-01-01T01:00:00 GMT, by their category: - - $ gcloud beta scc findings group 123456 --source=5678 \ - --group-by="category" \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" - - Group findings under organization 123456 and source 5678 into following 3 - state_changes (ADDED/CHANGED/UNCHANGED) based on the activity during past - 24 hours: - - $ gcloud beta scc findings group 123456 --source=5678 \ - --group-by="state_change" --compare-duration=86400s - Group findings under organization 123456 and location=eu across all sources by their category: @@ -77,16 +63,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -100,11 +87,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --filter=FILTER Expression that defines the filter to apply across findings. The @@ -156,9 +148,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/beta/scc/findings/list b/gcloud/beta/scc/findings/list index 9f43594f7..e84006d62 100644 --- a/gcloud/beta/scc/findings/list +++ b/gcloud/beta/scc/findings/list @@ -57,13 +57,7 @@ EXAMPLES under organization 123456: $ gcloud beta scc findings list 123456 --filter="state=\"ACTIVE\" \ - AND event_time > 1546304400000" - - List all findings that were ACTIVE as of 2019-01-01T01:00:00 GMT time, - under organization 123456: - - $ gcloud beta scc findings list 123456 \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + AND event_time > 1546304400000"" List all findings under organization 123456 across all sources and location=eu: @@ -86,16 +80,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -109,11 +104,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --field-mask=FIELD_MASK Field mask to specify the finding fields listed in the response. An @@ -152,9 +152,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/beta/scc/findings/list-marks b/gcloud/beta/scc/findings/list-marks index 0d310a4e5..209d69346 100644 --- a/gcloud/beta/scc/findings/list-marks +++ b/gcloud/beta/scc/findings/list-marks @@ -95,9 +95,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 6da62d339..f685d1be9 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -538,9 +538,9 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag can be repeated to specify multiple network interfaces. The following keys are allowed: @@ -593,6 +593,30 @@ FLAGS instance network interface IPv6 access config. IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index 9925237d6..4098b5232 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -27,6 +27,8 @@ SYNOPSIS [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -43,7 +45,10 @@ SYNOPSIS [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE - | --image-family=IMAGE_FAMILY] [--scopes=[SCOPE,...] | --no-scopes] + | --image-family=IMAGE_FAMILY] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] + [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -395,6 +400,19 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to the instance that + is created. The address must be the first IP address in the range or + from a /96 IP address range. This option can be used only when creating + a single instance. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range. It should be used together with --internal-ipv6-address. + Only /96 IP address range is supported and the default value is 96. If + not set, either the prefix length from --internal-ipv6-address will be + used or the default value of 96 will be assigned. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -489,8 +507,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -526,6 +547,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -730,6 +784,23 @@ FLAGS By default, debian-11 is assumed for this flag. + Specifies the reservation for instances created from this template. + + --reservation=RESERVATION + The name of the reservation, required when + --reservation-affinity=specific. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for instances created from this template. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index edb4621a7..66ef95b36 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -620,9 +620,9 @@ FLAGS Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, --private-network-ip, --stack-type, --ipv6-network-tier, - --ipv6-public-ptr-domain, --internal-ipv6-address, - --internal-ipv6-prefix-length, --ipv6-address, --ipv6-prefix-length, - --external-ipv6-address, --external-ipv6-prefix-length. This flag can + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length, --ipv6-public-ptr-domain. This flag can be repeated to specify multiple network interfaces. The following keys are allowed: @@ -675,6 +675,30 @@ FLAGS instance network interface IPv6 access config. IPV6_NETWORK_TIER must be PREMIUM (currently only one value is supported). + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + ipv6-public-ptr-domain Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, @@ -807,8 +831,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --source-machine-image=SOURCE_MACHINE_IMAGE The name of the machine image that the instance will be created from. diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 5d81df2d3..5d96d1599 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -30,6 +30,8 @@ SYNOPSIS [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] @@ -53,6 +55,8 @@ SYNOPSIS [--image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY] [--public-ptr | --no-public-ptr] [--public-ptr-domain=PUBLIC_PTR_DOMAIN | --no-public-ptr-domain] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [GCLOUD_WIDE_FLAG ...] @@ -445,6 +449,19 @@ FLAGS Default only for Spot VMs. Stop the VM without preserving memory. The VM can be restarted later. + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to the instance that + is created. The address must be the first IP address in the range or + from a /96 IP address range. This option can be used only when creating + a single instance. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range. It should be used together with --internal-ipv6-address. + Only /96 IP address range is supported and the default value is 96. If + not set, either the prefix length from --internal-ipv6-address will be + used or the default value of 96 will be assigned. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -545,8 +562,11 @@ FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any of these flags: --address, --network, --network-tier, --subnet, - --private-network-ip. This flag can be repeated to specify multiple - network interfaces. + --private-network-ip, --stack-type, --ipv6-network-tier, + --internal-ipv6-address, --internal-ipv6-prefix-length, --ipv6-address, + --ipv6-prefix-length, --external-ipv6-address, + --external-ipv6-prefix-length. This flag can be repeated to specify + multiple network interfaces. The following keys are allowed: address @@ -582,6 +602,39 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. + + ipv6-network-tier + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER + must be PREMIUM (currently only one value is supported). + + internal-ipv6-address + Assigns the given internal IPv6 address or range to the instance + that is created. The address must be the first IP address in the + range or from a /96 IP address range. This option can be used only + when creating a single instance. + + internal-ipv6-prefix-length + Optional field that indicates the prefix length of the internal + IPv6 address range. It should be used together with + internal-ipv6-address. Only /96 IP address range is supported and + the default value is 96. If not set, either the prefix length from + --internal-ipv6-address will be used or the default value of 96 + will be assigned. + + external-ipv6-address + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP address in the range. + This option can be used only when creating a single instance. + + external-ipv6-prefix-length + The prefix length of the external IPv6 address range. This field + should be used together with external-ipv6-address. Only the /96 IP + address range is supported, and the default value is 96. + aliases Specifies the IP alias ranges to allocate for this interface. If there are multiple IP alias ranges, they are separated by @@ -686,8 +739,7 @@ FLAGS The name of the instance template that the instance will be created from. An instance template can be a global/regional resource. - Users can also override machine type and labels. Values of other flags - will be ignored and --source-instance-template will be used instead. + Users can override instance properties using other flags. --stack-type=STACK_TYPE Specifies whether IPv6 is enabled on the default network interface. If @@ -861,6 +913,23 @@ FLAGS record for the external IP of the instance with the PTR domain name being the DNS name of the instance. + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when + --reservation-affinity=specific. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for the instance. RESERVATION_AFFINITY must + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + At most one of these can be specified: --scopes=[SCOPE,...] diff --git a/gcloud/compute/instances/help b/gcloud/compute/instances/help index e8ad877b9..4f07e1f22 100644 --- a/gcloud/compute/instances/help +++ b/gcloud/compute/instances/help @@ -108,7 +108,8 @@ COMMANDS List Compute Engine instances. move - Move an instance and its attached persistent disks between zones. + (DEPRECATED) Move an instance and its attached persistent disks between + zones. perform-maintenance Perform maintenance of Google Compute Engine instance. diff --git a/gcloud/compute/instances/move b/gcloud/compute/instances/move index aa68d5756..54f824f34 100644 --- a/gcloud/compute/instances/move +++ b/gcloud/compute/instances/move @@ -8,6 +8,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is deprecated. Please see + https://cloud.google.com/compute/docs/instances/moving-instance-across-zones + for an alternative method. + gcloud compute instances move moves a Compute Engine virtual machine from one zone to another. Moving a virtual machine might incur downtime if the guest OS must be shut down in order to quiesce disk volumes prior to diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index 1a62ad6fd..b62040064 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud compute public-delegated-prefixes create NAME --range=RANGE (--public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX | --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX) - [--description=DESCRIPTION] [--enable-live-migration] + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] + [--description=DESCRIPTION] [--enable-live-migration] [--mode=MODE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -36,12 +37,19 @@ REQUIRED FLAGS created from. OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + The allocatable prefix length supported by this PDP. + --description=DESCRIPTION Description of this public delegated prefix. --enable-live-migration Specify if this public delegated prefix is meant to be live migrated. + --mode=MODE + Specifies the mode of this IPv6 PDP. MODE must be one of: + EXTERNAL_IPV6_FORWARDING_RULE_CREATION, DELEGATION. + At most one of these can be specified: --global diff --git a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create index afc1983e8..12d117661 100644 --- a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud compute public-delegated-prefixes delegated-sub-prefixes create NAME - --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX [--create-addresses] - [--delegatee-project=DELEGATEE_PROJECT] [--description=DESCRIPTION] - [--range=RANGE] + --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] + [--create-addresses] [--delegatee-project=DELEGATEE_PROJECT] + [--description=DESCRIPTION] [--mode=MODE] [--range=RANGE] [--global-public-delegated-prefix | --public-delegated-prefix-region=PUBLIC_DELEGATED_PREFIX_REGION] [GCLOUD_WIDE_FLAG ...] @@ -39,6 +40,9 @@ REQUIRED FLAGS for. OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + Specify allocatable prefix length supported by this sub prefix. + --create-addresses Specify if the sub prefix is delegated to create address resources in the delegatee project. Default is false. @@ -50,6 +54,10 @@ OPTIONAL FLAGS --description=DESCRIPTION Description of the delegated sub prefix to create. + --mode=MODE + Specify mode for the sub prefix. MODE must be one of: DELEGATION, + EXTERNAL_IPV6_FORWARDING_RULE_CREATION. + --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. If not specified, the entire range ofthe public diff --git a/gcloud/compute/routers/add-bgp-peer b/gcloud/compute/routers/add-bgp-peer index 18f32181c..e8b8341f4 100644 --- a/gcloud/compute/routers/add-bgp-peer +++ b/gcloud/compute/routers/add-bgp-peer @@ -7,11 +7,14 @@ SYNOPSIS --peer-asn=PEER_ASN --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] - [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] - [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] + [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] + [--instance-zone=INSTANCE_ZONE] + [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-ip-address=PEER_IP_ADDRESS] + [--peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] @@ -66,6 +69,12 @@ OPTIONAL FLAGS Google-managed priority value of 100 is used. The routes with the lowest priority value win. + --[no-]enable-ipv4 + If IPv4 is enabled, the peer connection can be established with IPv4 + route exchange. If disabled, no IPv4 route exchange is allowed on any + active session. By default enabled for IPv4-based BGP sessions. Use + --enable-ipv4 to enable and --no-enable-ipv4 to disable. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -105,22 +114,37 @@ OPTIONAL FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + --ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned link-local IPv4 address in the range + 169.254.0.0/16 and must belong to the same subnet as the interface + address of the peer router. + --ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the Cloud Router interface for this BGP - peer. Must be a Google owned global unicast IPv6 address belonging to - the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and must - belong to same subnet as the interface address of the peer router. + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned global unicast IPv6 address belonging + to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and + must belong to same subnet as the interface address of the peer router. --md5-authentication-key=MD5_AUTHENTICATION_KEY The MD5 authentication key for this BGP peer. Maximum length is 80 characters. Can contain only printable ASCII characters. --peer-ip-address=PEER_IP_ADDRESS - The link-local address of the peer router. Must be a link-local IPv4 - address belonging to the range 169.254.0.0/16. + The address of the peer router. Must be a link-local IPv4 address in + the range 169.254.0.0/16 or an ULA IPv6 address in the range + fdff:1::/64. + + --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the peer router. Ignored otherwise. Must be a Google owned + link-local IPv4 address in the range 169.254.0.0/16. --peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the peer router. Must be a Google owned + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the peer router. Ignored otherwise. Must be a Google owned global unicast IPv6 address belonging to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64. diff --git a/gcloud/compute/routers/add-interface b/gcloud/compute/routers/add-interface index 024507cfb..9e97ff10c 100644 --- a/gcloud/compute/routers/add-interface +++ b/gcloud/compute/routers/add-interface @@ -8,9 +8,9 @@ SYNOPSIS --interconnect-attachment-region=INTERCONNECT_ATTACHMENT_REGION | --subnetwork=SUBNETWORK --subnetwork-region=SUBNETWORK_REGION | --vpn-tunnel=VPN_TUNNEL --vpn-tunnel-region=VPN_TUNNEL_REGION) - [--ip-address=IP_ADDRESS] [--mask-length=MASK_LENGTH] - [--redundant-interface=REDUNDANT_INTERFACE] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--ip-address=IP_ADDRESS] [--ip-version=IP_VERSION] + [--mask-length=MASK_LENGTH] [--redundant-interface=REDUNDANT_INTERFACE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute routers add-interface is used to add an interface to a @@ -58,12 +58,22 @@ REQUIRED FLAGS OPTIONAL FLAGS --ip-address=IP_ADDRESS - The link local address of the router for this interface. + The link local (IPv4) or ULA (IPv6) address of the router for this + interface. + + --ip-version=IP_VERSION + IP version of the interface. Possible values are IPV4 and IPV6. + Defaults to IPV4. IP_VERSION must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. --mask-length=MASK_LENGTH - The subnet mask for the link-local IP range of the interface. The - interface IP address and BGP peer IP address must be selected from the - subnet defined by this link-local range. + The subnet mask for the IP range of the interface. The interface IP + address and BGP peer IP address must be selected from the subnet + defined by this range. --redundant-interface=REDUNDANT_INTERFACE The interface that is redundant to the current interface. diff --git a/gcloud/compute/routers/create b/gcloud/compute/routers/create index e14c38d4c..cd9fb741d 100644 --- a/gcloud/compute/routers/create +++ b/gcloud/compute/routers/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute routers create NAME --network=NETWORK [--advertisement-mode=MODE] [--asn=ASN] [--async] + [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] [--description=DESCRIPTION] [--encrypted-interconnect-router] [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] @@ -40,6 +41,13 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --bgp-identifier-range=BGP_IDENTIFIER_RANGE + The range of valid BGP Identifiers for this Router. Must be a + link-local IPv4 range from 169.254.0.0/16, of size at least /30, even + if the BGP sessions are over IPv6. It must not overlap with any IPv4 + BGP session ranges. This is commonly called "router ID" by other + vendors. + --description=DESCRIPTION An optional description of this router. diff --git a/gcloud/compute/routers/update b/gcloud/compute/routers/update index c4dfda0d7..b2db6c89e 100644 --- a/gcloud/compute/routers/update +++ b/gcloud/compute/routers/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud compute routers update NAME [--advertisement-mode=MODE] [--asn=ASN] - [--async] [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--async] [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] + [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [--add-advertisement-groups=[GROUP,...] @@ -37,6 +38,13 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --bgp-identifier-range=BGP_IDENTIFIER_RANGE + The range of valid BGP Identifiers for this Router. Must be a + link-local IPv4 range from 169.254.0.0/16, of size at least /30, even + if the BGP sessions are over IPv6. It must not overlap with any IPv4 + BGP session ranges. This is commonly called "router ID" by other + vendors. + --keepalive-interval=KEEPALIVE_INTERVAL The interval between BGP keepalive messages that are sent to the peer. If set, this value must be between 20 and 60 seconds. The default is 20 diff --git a/gcloud/compute/routers/update-bgp-peer b/gcloud/compute/routers/update-bgp-peer index 85bc2b7a6..35f2f1cf5 100644 --- a/gcloud/compute/routers/update-bgp-peer +++ b/gcloud/compute/routers/update-bgp-peer @@ -6,11 +6,13 @@ SYNOPSIS gcloud compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] - [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] - [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] + [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] + [--ip-address=IP_ADDRESS] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] + [--peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] @@ -67,6 +69,12 @@ OPTIONAL FLAGS Google-managed priority value of 100 is used. The routes with the lowest priority value win. + --[no-]enable-ipv4 + If IPv4 is enabled, the peer connection can be established with IPv4 + route exchange. If disabled, no IPv4 route exchange is allowed on any + active session. Use --enable-ipv4 to enable and --no-enable-ipv4 to + disable. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -83,16 +91,24 @@ OPTIONAL FLAGS The name of the interface for this BGP peer. --ip-address=IP_ADDRESS - The link-local address of the Cloud Router interface for this BGP peer. - Must be a link-local IPv4 address belonging to the range 169.254.0.0/16 - and must belong to same subnet as the interface address of the peer - router. + The address of the Cloud Router interface for this BGP peer. Must be a + link-local IPv4 address in the range 169.254.0.0/16 or an ULA IPv6 + address in the range fdff:1::/64. It must also be in the same subnet as + the interface address of the peer router. + + --ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned link-local IPv4 address in the range + 169.254.0.0/16 and must belong to the same subnet as the interface + address of the peer router. --ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the Cloud Router interface for this BGP - peer. Must be a Google owned global unicast IPv6 address belonging to - the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and must - belong to same subnet as the interface address of the peer router. + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned global unicast IPv6 address belonging + to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and + must belong to same subnet as the interface address of the peer router. --md5-authentication-key=MD5_AUTHENTICATION_KEY The MD5 authentication key for this BGP peer. Maximum length is 80 @@ -104,11 +120,18 @@ OPTIONAL FLAGS https://tools.ietf.org/html/rfc6996, for example --asn=64512. --peer-ip-address=PEER_IP_ADDRESS - The link-local address of the peer router. Must be a link-local IPv4 - address belonging to the range 169.254.0.0/16. + The address of the peer router. Must be a link-local IPv4 address in + the range 169.254.0.0/16 or an ULA IPv6 address in the range + fdff:1::/64. + + --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the peer router. Ignored otherwise. Must be a Google owned + link-local IPv4 address in the range 169.254.0.0/16. --peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the peer router. Must be a Google owned + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the peer router. Ignored otherwise. Must be a Google owned global unicast IPv6 address belonging to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64. diff --git a/gcloud/compute/routers/update-interface b/gcloud/compute/routers/update-interface index 8da4314fa..717544b45 100644 --- a/gcloud/compute/routers/update-interface +++ b/gcloud/compute/routers/update-interface @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud compute routers update-interface NAME --interface-name=INTERFACE_NAME [--ip-address=IP_ADDRESS] - [--mask-length=MASK_LENGTH] [--region=REGION] + [--ip-version=IP_VERSION] [--mask-length=MASK_LENGTH] [--region=REGION] [--interconnect-attachment=INTERCONNECT_ATTACHMENT | --interconnect-attachment-region=INTERCONNECT_ATTACHMENT_REGION | --vpn-tunnel=VPN_TUNNEL | --vpn-tunnel-region=VPN_TUNNEL_REGION] @@ -25,12 +25,22 @@ REQUIRED FLAGS OPTIONAL FLAGS --ip-address=IP_ADDRESS - The link local address of the router for this interface. + The link local (IPv4) or ULA (IPv6) address of the router for this + interface. + + --ip-version=IP_VERSION + IP version of the interface. Possible values are IPV4 and IPV6. + Defaults to IPV4. IP_VERSION must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. --mask-length=MASK_LENGTH - The subnet mask for the link-local IP range of the interface. The - interface IP address and BGP peer IP address must be selected from the - subnet defined by this link-local range. + The subnet mask for the IP range of the interface. The interface IP + address and BGP peer IP address must be selected from the subnet + defined by this range. --region=REGION Region of the router to update. If not specified, you might be prompted diff --git a/gcloud/compute/sole-tenancy/node-groups/create b/gcloud/compute/sole-tenancy/node-groups/create index 5227de40f..edf3208b9 100644 --- a/gcloud/compute/sole-tenancy/node-groups/create +++ b/gcloud/compute/sole-tenancy/node-groups/create @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud compute sole-tenancy node-groups create NAME --node-template=NODE_TEMPLATE --target-size=TARGET_SIZE - [--description=DESCRIPTION] [--maintenance-policy=MAINTENANCE_POLICY] + [--description=DESCRIPTION] + [--maintenance-interval=MAINTENANCE_INTERVAL] + [--maintenance-policy=MAINTENANCE_POLICY] [--maintenance-window-start-time=START_TIME] [--zone=ZONE] [--autoscaler-mode=AUTOSCALER_MODE : --max-nodes=MAX_NODES --min-nodes=MIN_NODES] @@ -36,6 +38,20 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of this resource. + --maintenance-interval=MAINTENANCE_INTERVAL + Specifies the frequency of planned maintenance events. + MAINTENANCE_INTERVAL must be one of: + + as-needed + hosts are eligible to receive infrastructure and hypervisor updates + as they become available. + recurrent + hosts receive planned infrastructure and hypervisor updates on a + periodic basis, but not more frequently than every 28 days. This + minimizes the number of planned maintenance operations on + individual hosts and reduces the frequency of disruptions, both + live migrations and terminations, on individual VMs. + --maintenance-policy=MAINTENANCE_POLICY Determines the maintenance behavior during host maintenance events. For more information, see diff --git a/gcloud/compute/sole-tenancy/node-groups/help b/gcloud/compute/sole-tenancy/node-groups/help index 33fb92ead..66ba8d406 100644 --- a/gcloud/compute/sole-tenancy/node-groups/help +++ b/gcloud/compute/sole-tenancy/node-groups/help @@ -37,6 +37,9 @@ COMMANDS list-nodes List Compute Engine sole-tenant nodes present in a nodegroup. + perform-maintenance + Perform maintenance on nodes in a Compute Engine node group. + remove-iam-policy-binding Remove IAM policy binding from a Compute Engine node group. diff --git a/gcloud/compute/sole-tenancy/node-groups/perform-maintenance b/gcloud/compute/sole-tenancy/node-groups/perform-maintenance new file mode 100644 index 000000000..f64c11775 --- /dev/null +++ b/gcloud/compute/sole-tenancy/node-groups/perform-maintenance @@ -0,0 +1,68 @@ +NAME + gcloud compute sole-tenancy node-groups perform-maintenance - perform + maintenance on nodes in a Compute Engine node group + +SYNOPSIS + gcloud compute sole-tenancy node-groups perform-maintenance NAME + --nodes=NODE,[NODE,...] [--start-time=START_TIME] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Perform maintenance on nodes in a Compute Engine node group. + +EXAMPLES + To perform maintenance on nodes in a node group, run: + + $ gcloud compute sole-tenancy node-groups perform-maintenance \ + my-node-group --nodes=node-1,node-2 \ + --start-time=2023-05-01T00:00:00.000-08:00 + +POSITIONAL ARGUMENTS + NAME + Name of the node group to operate on. + +REQUIRED FLAGS + --nodes=NODE,[NODE,...] + The names of the nodes to perform maintenance on. + +OPTIONAL FLAGS + --start-time=START_TIME + The requested time for the maintenance window to start. The timestamp + must be an RFC3339 valid string. + + --zone=ZONE + Zone of the node group to operate on. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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 compute sole-tenancy node-groups perform-maintenance + + $ gcloud beta compute sole-tenancy node-groups perform-maintenance + diff --git a/gcloud/dataplex/entries/create b/gcloud/dataplex/entries/create new file mode 100644 index 000000000..045f326d6 --- /dev/null +++ b/gcloud/dataplex/entries/create @@ -0,0 +1,290 @@ +NAME + gcloud dataplex entries create - create a Dataplex Entry resource + +SYNOPSIS + gcloud dataplex entries create + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + (--entry-type=ENTRY_TYPE : --entry-type-location=ENTRY_TYPE_LOCATION + --entry-type-project=ENTRY_TYPE_PROJECT) + [--aspects=YAML_OR_JSON_FILE] + [--fully-qualified-name=FULLY_QUALIFIED_NAME] + [--parent-entry=PARENT_ENTRY] + [--entry-source-ancestors=[ANCESTORS,...] + --entry-source-create-time=DATE_TIME + --entry-source-description=DESCRIPTION + --entry-source-display-name=DISPLAY_NAME + --entry-source-labels=[KEY=VALUE,...] + --entry-source-platform=PLATFORM_NAME + --entry-source-resource=RESOURCE --entry-source-system=SYSTEM_NAME + --entry-source-update-time=DATE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Dataplex Entry resource. + +EXAMPLES + To create a Dataplex entry with name my-dataplex-entry in location + us-central1 in entry group my-entry-group and with entry type + projects/my-project/locations/us-central1/entryTypes/my-type, run: + + $ gcloud dataplex entries create my-dataplex-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type + + To create a Dataplex Entry with name my-child-entry and set its parent to + an existing entry my-parent-entry, run: + + $ gcloud dataplex entries create my-child-entry \ + --location=us-central --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --parent-entry \ + projects/my-project/locations/us-central1/entryGroups/\ + my-entry-group/entries/my-parent-entry + + To create a Dataplex Entry with its description, display name, ancestors, + labels and timestamps populated in its EntrySource, run: + + $ gcloud dataplex entries create my-entry --location=us-central \ + --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --entry-source-description \ + 'This is a description of the Entry.' \ + --entry-source-display-name 'display name' \ + --entry-source-ancestors \ + '{"type":"projects/my-project/locations/us-central1/entryTypes/s\ + ome-type", + "name":"projects/my-project/locations/us-central1/entryGroups/my-en\ + try-group/entries/ancestor-entry"}, + {"type":"projects/my-project/locations/us-central1/entryTypes/anoth\ + er-type", + "name":"projects/my-project/locations/us-central1/entryGroups/my-en\ + try-group/entries/another-ancestor-entry"}' \ + --entry-source-labels key1=value1,key2=value2 \ + --entry-source-create-time 2024-01-01T09:39:25.160173Z \ + --entry-source-update-time 2024-01-01T09:39:25.160173Z + + To create a Dataplex Entry reading its aspects from a YAML file, run: + + $ gcloud dataplex entries create my-entry --location=us-central \ + --entry_group=my-entry-group \ + --entry-type \ + projects/my-project/locations/us-central1/entryTypes/my-type \ + --aspects aspects.yaml + + The file containing the aspects has the following format: + + my-project.us-central1.my-aspect-type: + aspectType: my-project.us-central1.my-aspect-type + createTime: "2024-01-01T09:39:25.160173Z" + updateTime: "2024-01-01T09:39:25.160173Z" + data: + {} + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + Entry type resource - Arguments and flags that define the Dataplex + EntryType you want to reference. The arguments in this group can be used + to specify the attributes of this resource. + + This must be specified. + + --entry-type=ENTRY_TYPE + ID of the entry type or fully qualified identifier for the entry + type. + + To set the entry_type attribute: + ▸ provide the argument --entry-type on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entry-type-location=ENTRY_TYPE_LOCATION + The location of the EntryType resource. + + To set the entry-type-location attribute: + ▸ provide the argument --entry-type on the command line with a + fully specified name; + ▸ provide the argument --entry-type-location on the command line. + + --entry-type-project=ENTRY_TYPE_PROJECT + The project of the EntryType resource. + + To set the entry-type-project attribute: + ▸ provide the argument --entry-type on the command line with a + fully specified name; + ▸ provide the argument --entry-type-project on the command line. + +OPTIONAL FLAGS + --aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + --fully-qualified-name=FULLY_QUALIFIED_NAME + A name for the entry that can reference it in an external system. The + maximum size of the field is 4000 characters. + + Entry resource - Arguments and flags that define the parent Entry you want + to reference. 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 --parent-entry on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + To set the location attribute: + ◆ provide the argument --parent-entry on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property dataplex/location. + + To set the entry_group attribute: + ◆ provide the argument --parent-entry on the command line with a fully + specified name; + ◆ provide the argument --entry_group on the command line. + + --parent-entry=PARENT_ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument --parent-entry on the command line. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-ancestors=[ANCESTORS,...] + Information about individual items in the hierarchy of an Entry. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + --entry-source-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. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + +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 variant is also available: + + $ gcloud alpha dataplex entries create + diff --git a/gcloud/dataplex/entries/delete b/gcloud/dataplex/entries/delete new file mode 100644 index 000000000..750246d8b --- /dev/null +++ b/gcloud/dataplex/entries/delete @@ -0,0 +1,73 @@ +NAME + gcloud dataplex entries delete - delete a Dataplex entry + +SYNOPSIS + gcloud dataplex entries delete + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Dataplex entry. + +EXAMPLES + To delete the entry 'entry1', run: + + $ gcloud dataplex entries delete entry1 --entry-group=entry-group1 \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Entry 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries delete + diff --git a/gcloud/dataplex/entries/describe b/gcloud/dataplex/entries/describe new file mode 100644 index 000000000..c28ad679f --- /dev/null +++ b/gcloud/dataplex/entries/describe @@ -0,0 +1,124 @@ +NAME + gcloud dataplex entries describe - describe a Dataplex entry + +SYNOPSIS + gcloud dataplex entries describe + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--aspect-types=[ASPECT_TYPES,...]] [--paths=[PATHS,...]] [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Dataplex entry. + + Displays the details of a Dataplex entry resource given a valid entry ID. + +EXAMPLES + To describe a Dataplex entry entry1 within entry group entry-group1 in + location us-central1, run: + + $ gcloud dataplex entries describe entry1 \ + --entry-group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --aspect-types=[ASPECT_TYPES,...] + Limits the aspects returned to the provided aspect types. Only works if + the --view=custom is selected. + + For example, if two aspect types are specified: + "projects/projectA/locations/us-central1/my-aspect-type,projects/projectB/locations/us/my-aspect-type2" + then only aspects matching these aspect types will be returned. + + Can be further constrained by the --paths argument. + + --paths=[PATHS,...] + Limits the aspects returned to those associated with the provided paths + within the Entry. Only works if the --view=custom is selected. + + For example, if two paths are specified: "--paths=property1,property2" + then only aspects on these paths will be returned. + + To return aspects without any path, the empty (root) path can be + specified. For this "." can be used. For example, when + "--paths=.,property1" are specified, then only aspects on the path + "property1" and on the entry itself will be returned. + + Can be further constrained by --aspect-types argument. + + --view=VIEW + Controls which parts of an entry are to be returned. VIEW must be one + of: + + all + Returns all aspects. If the number of aspects would exceed 100, the + first 100 will be returned. + + basic + Returns entry only, without aspects. + custom + Returns aspects filtered based on --aspect-types AND --paths + arguments specified. When used, at least one of --aspect-types and + --paths arguments must be specified. If the number of aspects would + exceed 100, the first 100 will be returned. + + full + Default value. Returns all required aspects, as well as the keys of + all non-required aspects. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries describe + diff --git a/gcloud/dataplex/entries/help b/gcloud/dataplex/entries/help new file mode 100644 index 000000000..2fdf709a9 --- /dev/null +++ b/gcloud/dataplex/entries/help @@ -0,0 +1,46 @@ +NAME + gcloud dataplex entries - manage Dataplex Catalog Entries resources + +SYNOPSIS + gcloud dataplex entries COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Dataplex Catalog Entries resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Dataplex Entry resource. + + delete + Delete a Dataplex entry. + + describe + Describe a Dataplex entry. + + list + List Dataplex entries. + + lookup + Lookup a Dataplex entry. + + remove-aspects + Remove aspects from a Dataplex Entry. + + update + Update a Dataplex Entry. + + update-aspects + Add or update aspects for a Dataplex Entry. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries + diff --git a/gcloud/dataplex/entries/list b/gcloud/dataplex/entries/list new file mode 100644 index 000000000..85f5deda4 --- /dev/null +++ b/gcloud/dataplex/entries/list @@ -0,0 +1,100 @@ +NAME + gcloud dataplex entries list - list Dataplex entries + +SYNOPSIS + gcloud dataplex entries list + (--entry-group=ENTRY_GROUP : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Dataplex entries in an entry group. + +EXAMPLES + To List the entries in entry group 'entry-group1', run: + + $ gcloud dataplex entries list --entry-group=entry-group1 \ + --location=us-central1 --project=test-project + +REQUIRED FLAGS + Entry group resource - Example Entry Group to list all contained Entries. + 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 --entry-group 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. + + --entry-group=ENTRY_GROUP + ID of the entry group or fully qualified identifier for the entry + group. + + To set the entry-group attribute: + ▸ provide the argument --entry-group on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument --entry-group on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries list + diff --git a/gcloud/dataplex/entries/lookup b/gcloud/dataplex/entries/lookup new file mode 100644 index 000000000..89c69287f --- /dev/null +++ b/gcloud/dataplex/entries/lookup @@ -0,0 +1,127 @@ +NAME + gcloud dataplex entries lookup - lookup a Dataplex entry + +SYNOPSIS + gcloud dataplex entries lookup + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--aspect-types=[ASPECT_TYPES,...]] [--paths=[PATHS,...]] [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lookup a Dataplex entry. + + Displays the details of a Dataplex entry resource given a valid entry ID. + Unlike describe, where the Dataplex permission is required for access, for + lookup the permission from the original source system is required on the + entry instead. For example, if the source is a BigQuery table, you need the + bigquery.tables.get permission to lookup an entry. + +EXAMPLES + To lookup a Dataplex entry entry1 within entry group entry-group1 in + location us-central1, run: + + $ gcloud dataplex entries lookup entry1 --entry-group=entry-group1 \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to lookup. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --aspect-types=[ASPECT_TYPES,...] + Limits the aspects returned to the provided aspect types. Only works if + the --view=custom is selected. + + For example, if two aspect types are specified: + "projects/projectA/locations/us-central1/my-aspect-type,projects/projectB/locations/us/my-aspect-type2" + then only aspects matching these aspect types will be returned. + + Can be further constrained by the --paths argument. + + --paths=[PATHS,...] + Limits the aspects returned to those associated with the provided paths + within the Entry. Only works if the --view=custom is selected. + + For example, if two paths are specified: "--paths=property1,property2" + then only aspects on these paths will be returned. + + To return aspects without any path, the empty (root) path can be + specified. For this "." can be used. For example, when + "--paths=.,property1" are specified, then only aspects on the path + "property1" and on the entry itself will be returned. + + Can be further constrained by --aspect-types argument. + + --view=VIEW + Controls which parts of an entry are to be returned. VIEW must be one + of: + + all + Returns all aspects. If the number of aspects would exceed 100, the + first 100 will be returned. + + basic + Returns entry only, without aspects. + custom + Returns aspects filtered based on --aspect-types AND --paths + arguments specified. When used, at least one of --aspect-types and + --paths arguments must be specified. If the number of aspects would + exceed 100, the first 100 will be returned. + + full + Default value. Returns all required aspects, as well as the keys of + all non-required aspects. + +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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries lookup + diff --git a/gcloud/dataplex/entries/remove-aspects b/gcloud/dataplex/entries/remove-aspects new file mode 100644 index 000000000..601d60d70 --- /dev/null +++ b/gcloud/dataplex/entries/remove-aspects @@ -0,0 +1,110 @@ +NAME + gcloud dataplex entries remove-aspects - remove aspects from a Dataplex + Entry + +SYNOPSIS + gcloud dataplex entries remove-aspects + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + --keys=[ASPECT_TYPE@PATH,...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove aspects from a Dataplex Entry. + +EXAMPLES + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --keys='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --keys='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud dataplex entries remove-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --keys=test-project.us-central1.some-aspect-type@Schema.column1,\ + test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --keys=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + +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 variant is also available: + + $ gcloud alpha dataplex entries remove-aspects + diff --git a/gcloud/dataplex/entries/update b/gcloud/dataplex/entries/update new file mode 100644 index 000000000..d2b49b634 --- /dev/null +++ b/gcloud/dataplex/entries/update @@ -0,0 +1,288 @@ +NAME + gcloud dataplex entries update - update a Dataplex Entry + +SYNOPSIS + gcloud dataplex entries update + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--remove-aspects=[ASPECT_TYPE@PATH,...]] + [--update-aspects=YAML_OR_JSON_FILE] + [--clear-fully-qualified-name + | --fully-qualified-name=FULLY_QUALIFIED_NAME] + [--entry-source-update-time=DATE_TIME + : --clear-entry-source-create-time + | --entry-source-create-time=DATE_TIME + --clear-entry-source-description + | --entry-source-description=DESCRIPTION + --clear-entry-source-display-name + | --entry-source-display-name=DISPLAY_NAME + --clear-entry-source-labels + | --entry-source-labels=[KEY=VALUE,...] --clear-entry-source-platform + | --entry-source-platform=PLATFORM_NAME --clear-entry-source-resource + | --entry-source-resource=RESOURCE --clear-entry-source-system + | --entry-source-system=SYSTEM_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update specified fields in a given Dataplex Entry. + +EXAMPLES + To update fully qualified name (FQN) of an entry, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --fully-qualified-name='custom:a.b.c' + + To update description of an entry, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --entry-source-description='Updated description' \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To clear the description of an entry, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --clear-entry-source-description \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To add or update aspects from the YAML/JSON file, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --update-aspects=path-to-a-file-with-aspects.json + + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud dataplex entries update entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects=test-project.us-central1.some-aspect-type@Schem\ + a.column1,test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --remove-aspects=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + --update-aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + At most one of these can be specified: + + --clear-fully-qualified-name + Clear the FQN for the Entry. + + --fully-qualified-name=FULLY_QUALIFIED_NAME + FQN, a name for the entry that can reference it in an external + system. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + At most one of these can be specified: + + --clear-entry-source-create-time + Clear the value for the create_time field in the Entry Source. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-description + Clear the value for the description field in the Entry Source. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + At most one of these can be specified: + + --clear-entry-source-display-name + Clear the value for the display_name field in the Entry Source. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + At most one of these can be specified: + + --clear-entry-source-labels + Clear the labels for the Entry Source. + + --entry-source-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. + + At most one of these can be specified: + + --clear-entry-source-platform + Clear the value for the platform field in the Entry Source. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + At most one of these can be specified: + + --clear-entry-source-resource + Clear the value for the resource field in the Entry Source. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-system + Clear the value for the system field in the Entry Source. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + +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 variant is also available: + + $ gcloud alpha dataplex entries update + diff --git a/gcloud/dataplex/entries/update-aspects b/gcloud/dataplex/entries/update-aspects new file mode 100644 index 000000000..a48a8d126 --- /dev/null +++ b/gcloud/dataplex/entries/update-aspects @@ -0,0 +1,127 @@ +NAME + gcloud dataplex entries update-aspects - add or update aspects for a + Dataplex Entry + +SYNOPSIS + gcloud dataplex entries update-aspects + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + --aspects=YAML_OR_JSON_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add or update aspects for a Dataplex Entry. + +EXAMPLES + To add or update aspects for the Dataplex entry entry1 within the entry + group entry-group1 in location us-central1 from the YAML/JSON file, run: + + $ gcloud dataplex entries update-aspects entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --aspects=path-to-a-file-with-aspects.json + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + +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 variant is also available: + + $ gcloud alpha dataplex entries update-aspects + diff --git a/gcloud/dataplex/help b/gcloud/dataplex/help index fa53234cf..c139a8ee2 100644 --- a/gcloud/dataplex/help +++ b/gcloud/dataplex/help @@ -24,6 +24,9 @@ GROUPS datascans Manage Dataplex Datascan. + entries + Manage Dataplex Catalog Entries resources. + environments Manage Dataplex Environments. diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 9fda92089..92af7ec90 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -429,6 +429,12 @@ FLAGS --clear-max-instances Clears the maximum instances setting for the function. + If it's any 2nd gen function or a 1st gen HTTP function, this flag + sets maximum instances to 0, which means there is no limit to maximum + instances. If it's an event-driven 1st gen function, this flag sets + maximum instances to 3000, which is the default value for 1st gen + functions. + --max-instances=MAX_INSTANCES Sets the maximum number of instances for the function. A function execution that would exceed max-instances times out. diff --git a/gcloud/infra-manager/deployments/apply b/gcloud/infra-manager/deployments/apply index 09845f66b..c8d5acb2a 100644 --- a/gcloud/infra-manager/deployments/apply +++ b/gcloud/infra-manager/deployments/apply @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud infra-manager deployments apply (DEPLOYMENT : --location=LOCATION) + [--annotations=[KEY=VALUE,...]] [--artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET] [--async] [--import-existing-resources] [--labels=[KEY=VALUE,...]] [--quota-validation=QUOTA_VALIDATION] @@ -79,6 +80,31 @@ POSITIONAL ARGUMENTS ▸ set the property infra-manager/location. FLAGS + --annotations=[KEY=VALUE,...] + Annotations to apply to the deployment. Existing values are + overwritten. To retain the existing annotations on a deployment, do not + specify this flag. + + Examples: + + Update annotations for an existing deployment: + + $ gcloud infra-manager deployments apply \ + projects/p1/locations/us-central1/deployments/my-deployment \ + --gcs-source="gs://my-bucket" \ + --annotations="env=prod,team=finance" + + Clear annotations for an existing deployment: + + $ gcloud infra-manager deployments apply \ + projects/p1/locations/us-central1/deployments/my-deployment \ + --gcs-source="gs://my-bucket" --annotations="" + + Add an annotation to an existing deployment: + + First, fetch the current annotations using the `describe` command, then follow the + preceding example for updating annotations. + --artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET user-defined location of Cloud Build logs, artifacts, and Terraform state files in Google Cloud Storage. Format: gs://{bucket}/{folder} A diff --git a/gcloud/infra-manager/previews/create b/gcloud/infra-manager/previews/create index a8832a8f0..41fd95546 100644 --- a/gcloud/infra-manager/previews/create +++ b/gcloud/infra-manager/previews/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud infra-manager previews create [PREVIEW] + [--annotations=[KEY=VALUE,...]] [--artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET] [--async] [--deployment=DEPLOYMENT] [--labels=[KEY=VALUE,...]] [--location=LOCATION] [--preview-mode=PREVIEW_MODE] @@ -59,6 +60,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument PREVIEW on the command line. FLAGS + --annotations=[KEY=VALUE,...] + Preview annotations cannot be updated after creation. + --artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET user-defined location of Cloud Build logs, artifacts, and Terraform state files in Google Cloud Storage. Format: gs://{bucket}/{folder} A @@ -72,27 +76,7 @@ FLAGS Deployment reference for preview. --labels=[KEY=VALUE,...] - Labels to apply to the preview. Existing values are overwritten. To - retain the existing labels on a preview, do not specify this flag. - - Examples: - - Update labels for an existing preview: - - $ gcloud infra-manager previews create \ - projects/p1/locations/us-central1/previews/my-preview \ - --gcs-source="gs://my-bucket" --labels="env=prod,team=finance" - - Clear labels for an existing preview: - - $ gcloud infra-manager previews create \ - projects/p1/locations/us-central1/previews/my-preview \ - --gcs-source="gs://my-bucket" --labels="" - - Add a label to an existing preview: - - First, fetch the current labels using the `describe` command, then follow the - preceding example for updating labels. + Preview labels cannot be updated after creation. Location resource - the location to be used as parent. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this diff --git a/gcloud/kms/keys/create b/gcloud/kms/keys/create index 871d58bff..9323d3509 100644 --- a/gcloud/kms/keys/create +++ b/gcloud/kms/keys/create @@ -168,19 +168,19 @@ OPTIONAL FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --destroy-scheduled-duration=DESTROY_SCHEDULED_DURATION The amount of time that versions of the key should spend in the diff --git a/gcloud/kms/keys/update b/gcloud/kms/keys/update index b91c89e62..b6cfcd1d5 100644 --- a/gcloud/kms/keys/update +++ b/gcloud/kms/keys/update @@ -117,19 +117,19 @@ FLAGS choosing an algorithm, see https://cloud.google.com/kms/docs/algorithms. DEFAULT_ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, - aes-256-ctr, aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, - ec-sign-secp256k1-sha256, external-symmetric-encryption, - google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, - hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, - rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, - rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, - rsa-decrypt-oaep-4096-sha256, rsa-decrypt-oaep-4096-sha512, - rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, - rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, - rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512, - rsa-sign-raw-pkcs1-2048, rsa-sign-raw-pkcs1-3072, - rsa-sign-raw-pkcs1-4096. + aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, + ec-sign-p384-sha384, ec-sign-secp256k1-sha256, + external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, + rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, + rsa-decrypt-oaep-4096-sha1, rsa-decrypt-oaep-4096-sha256, + rsa-decrypt-oaep-4096-sha512, rsa-sign-pkcs1-2048-sha256, + rsa-sign-pkcs1-3072-sha256, rsa-sign-pkcs1-4096-sha256, + rsa-sign-pkcs1-4096-sha512, rsa-sign-pss-2048-sha256, + rsa-sign-pss-3072-sha256, rsa-sign-pss-4096-sha256, + rsa-sign-pss-4096-sha512, rsa-sign-raw-pkcs1-2048, + rsa-sign-raw-pkcs1-3072, rsa-sign-raw-pkcs1-4096. --next-rotation-time=NEXT_ROTATION_TIME Next automatic rotation time of the key. See $ gcloud topic datetimes diff --git a/gcloud/kms/keys/versions/import b/gcloud/kms/keys/versions/import index e818d5702..6195af20b 100644 --- a/gcloud/kms/keys/versions/import +++ b/gcloud/kms/keys/versions/import @@ -32,7 +32,7 @@ REQUIRED FLAGS about supported algorithms, see https://cloud.google.com/kms/docs/algorithms. ALGORITHM must be one of: aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, - aes-256-gcm, ec-sign-p256-sha256, ec-sign-p384-sha384, + aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, diff --git a/gcloud/logging/views/add-iam-policy-binding b/gcloud/logging/views/add-iam-policy-binding new file mode 100644 index 000000000..606f252c5 --- /dev/null +++ b/gcloud/logging/views/add-iam-policy-binding @@ -0,0 +1,135 @@ +NAME + gcloud logging views add-iam-policy-binding - add IAM policy binding to a + log view + +SYNOPSIS + gcloud logging views add-iam-policy-binding VIEW_ID --bucket=BUCKET + --location=LOCATION --member=PRINCIPAL --role=ROLE + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add IAM policy binding to a log view. + +EXAMPLES + To add an IAM policy binding for the role 'roles/my-role' for the user + 'my-user@gmail.com' on my-view, run: + + $ gcloud logging views add-iam-policy-binding my-view \ + --member='user:my-user@gmail.com' --role='roles/my-role' \ + --bucket=my-bucket --location=global + + To add a binding with a condition, run: + + $ gcloud logging views add-iam-policy-binding my-view \ + --member='user:my-user@gmail.com' --role='roles/my-role' \ + --bucket=my-bucket --location=global \ + --condition=expression=[expression],title=[title],\ + description=[description] + + See https://cloud.google.com/iam/docs/managing-policies for details about + IAM policies and member types. + +POSITIONAL ARGUMENTS + VIEW_ID + ID of the view that contains the IAM policy. + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that contains the view. + + --location=LOCATION + Location of the bucket that contains the view. + + --member=PRINCIPAL + The principal to add the binding for. 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. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the view that contains the IAM policy. + + --folder=FOLDER_ID + Folder of the view that contains the IAM policy. + + --organization=ORGANIZATION_ID + Organization of the view that contains the IAM policy. + + --project=PROJECT_ID + Project of the view that contains the IAM policy. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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. diff --git a/gcloud/logging/views/describe b/gcloud/logging/views/describe index cb749c922..b657e32d3 100644 --- a/gcloud/logging/views/describe +++ b/gcloud/logging/views/describe @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Displays information about a view. + Displays information about a log view. EXAMPLES To describe a view in a project, run: diff --git a/gcloud/logging/views/get-iam-policy b/gcloud/logging/views/get-iam-policy new file mode 100644 index 000000000..b8ac0757c --- /dev/null +++ b/gcloud/logging/views/get-iam-policy @@ -0,0 +1,63 @@ +NAME + gcloud logging views get-iam-policy - display the IAM policy for a view + +SYNOPSIS + gcloud logging views get-iam-policy VIEW_ID --bucket=BUCKET + --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the IAM policy for a view. + +EXAMPLES + To describe a view in a project, run: + + $ gcloud logging views get-iam-policy my-view --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + VIEW_ID + ID of the view to fetch IAM policy + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that holds the view. + + --location=LOCATION + Location of the bucket that contains the view + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the view to fetch IAM policy. + + --folder=FOLDER_ID + Folder of the view to fetch IAM policy. + + --organization=ORGANIZATION_ID + Organization of the view to fetch IAM policy. + + --project=PROJECT_ID + Project of the view to fetch IAM policy. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/views/help b/gcloud/logging/views/help index a720c8def..8c12a6ced 100644 --- a/gcloud/logging/views/help +++ b/gcloud/logging/views/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + Add IAM policy binding to a log view. + create Create a log view on a log bucket. @@ -25,9 +28,18 @@ COMMANDS describe Display information about a view. + get-iam-policy + Display the IAM policy for a view. + list List the defined views. + remove-iam-policy-binding + Remove IAM policy binding to a log view. + + set-iam-policy + Set IAM policy for a view. + update Update a view. diff --git a/gcloud/logging/views/remove-iam-policy-binding b/gcloud/logging/views/remove-iam-policy-binding new file mode 100644 index 000000000..dcfdba8b0 --- /dev/null +++ b/gcloud/logging/views/remove-iam-policy-binding @@ -0,0 +1,141 @@ +NAME + gcloud logging views remove-iam-policy-binding - remove IAM policy binding + to a log view + +SYNOPSIS + gcloud logging views remove-iam-policy-binding VIEW_ID --bucket=BUCKET + --location=LOCATION --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove IAM policy binding to a log view. + +EXAMPLES + To remove an IAM policy binding for the role 'roles/my-role' for the user + 'my-user@gmail.com' on my-view, run: + + $ gcloud logging views remove-iam-policy-binding my-view \ + --member='user:my-user@gmail.com' --role='roles/my-role' \ + --bucket=my-bucket --location=global + + To remove a binding with a condition, run: + + $ gcloud logging views remove-iam-policy-binding my-view \ + --member='user:my-user@gmail.com' --role='roles/my-role' \ + --bucket=my-bucket --location=global \ + --condition=expression=[expression],title=[title],\ + description=[description] + + See https://cloud.google.com/iam/docs/managing-policies for details about + IAM policies and member types. + +POSITIONAL ARGUMENTS + VIEW_ID + ID of the view that contains the IAM policy. + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that contains the view. + + --location=LOCATION + Location of the bucket that contains the view. + + --member=PRINCIPAL + The principal to remove the binding for. 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. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the view that contains the IAM policy. + + --folder=FOLDER_ID + Folder of the view that contains the IAM policy. + + --organization=ORGANIZATION_ID + Organization of the view that contains the IAM policy. + + --project=PROJECT_ID + Project of the view that contains the IAM policy. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/views/set-iam-policy b/gcloud/logging/views/set-iam-policy new file mode 100644 index 000000000..1f4b93dba --- /dev/null +++ b/gcloud/logging/views/set-iam-policy @@ -0,0 +1,71 @@ +NAME + gcloud logging views set-iam-policy - set IAM policy for a view + +SYNOPSIS + gcloud logging views set-iam-policy VIEW_ID POLICY_FILE --bucket=BUCKET + --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set an IAM policy for a view. + +EXAMPLES + To set the IAM policy using a json file 'my_policy.json' for the view + my-view in my-bucket in the global location, run: + + $ gcloud logging views set-iam-policy my-view \ + /path/to/my_policy.json --bucket=my-bucket --location=global + +POSITIONAL ARGUMENTS + VIEW_ID + ID of the view to set IAM policy. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that contains the view. + + --location=LOCATION + Location of the bucket that contains the view. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the view to set IAM policy. + + --folder=FOLDER_ID + Folder of the view to set IAM policy. + + --organization=ORGANIZATION_ID + Organization of the view to set IAM policy. + + --project=PROJECT_ID + Project of the view to set IAM policy. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/scc/findings/group b/gcloud/scc/findings/group index 58b04a66f..ac6ec99fd 100644 --- a/gcloud/scc/findings/group +++ b/gcloud/scc/findings/group @@ -40,20 +40,6 @@ EXAMPLES $ gcloud scc findings group 123456 --source=5678 \ --group-by="category" --filter="state=\"ACTIVE\"" - Group ACTIVE findings under organization 123456 and source 5678, on - 2019-01-01T01:00:00 GMT, by their category: - - $ gcloud scc findings group 123456 --source=5678 \ - --group-by="category" \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" - - Group findings under organization 123456 and source 5678 into following 3 - state_changes (ADDED/CHANGED/UNCHANGED) based on the activity during past - 24 hours: - - $ gcloud scc findings group 123456 --source=5678 \ - --group-by="state_change" --compare-duration=86400s - Group findings under organization 123456 and location=eu across all sources by their category: @@ -76,16 +62,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -99,11 +86,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --filter=FILTER Expression that defines the filter to apply across findings. The @@ -155,9 +147,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/scc/findings/list b/gcloud/scc/findings/list index 7d53dfe3a..3b0236866 100644 --- a/gcloud/scc/findings/list +++ b/gcloud/scc/findings/list @@ -54,13 +54,7 @@ EXAMPLES under organization 123456: $ gcloud scc findings list 123456 --filter="state=\"ACTIVE\" AND \ - event_time > 1546304400000" - - List all findings that were ACTIVE as of 2019-01-01T01:00:00 GMT time, - under organization 123456: - - $ gcloud scc findings list 123456 \ - --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + event_time > 1546304400000"" List all findings under organization 123456 across all sources and location=eu: @@ -83,16 +77,17 @@ POSITIONAL ARGUMENTS FLAGS --compare-duration=COMPARE_DURATION - When compare_duration is set, the result's "state_change" attribute is - updated to indicate whether the finding had its state changed, the - finding's state remained unchanged, or if the finding was added during - the compare_duration period of time that precedes the read_time. This - is the time between (read_time - compare_duration) and read_time. The - state_change value is derived based on the presence and state of the - finding at the two points in time. Intermediate state changes between - the two times don't affect the result. For example, the results aren't - affected if the finding is made inactive and then active again. - Possible "state_change" values when compare_duration is specified: + (DEPRECATED) When compare_duration is set, the result's "state_change" + attribute is updated to indicate whether the finding had its state + changed, the finding's state remained unchanged, or if the finding was + added during the compare_duration period of time that precedes the + read_time. This is the time between (read_time - compare_duration) and + read_time. The state_change value is derived based on the presence and + state of the finding at the two points in time. Intermediate state + changes between the two times don't affect the result. For example, the + results aren't affected if the finding is made inactive and then active + again. Possible "state_change" values when compare_duration is + specified: ◆ 'CHANGED': indicates that the finding was present at the start of compare_duration, but changed its state at read_time. @@ -106,11 +101,16 @@ FLAGS ◆ 'REMOVED': indicates that the finding was present at the start of compare_duration, but was not present at read_time. - If compare_duration is not specified, then the only possible - state_change is 'UNUSED', which will be the state_change set for all - findings present at read_time. If this field is set then 'state_change' - must be a specified field in 'group_by'. See $ gcloud topic datetimes - for information on supported duration formats. + If compare_duration is not specified, then the only possible + state_change is 'UNUSED', which will be the state_change set for all + findings present at read_time. If this field is set then 'state_change' + must be a specified field in 'group_by'. See $ gcloud topic datetimes + for information on supported duration formats. + + The --compare-duration option is deprecated. For more information, [see + the deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --field-mask=FIELD_MASK Field mask to specify the finding fields listed in the response. An @@ -149,9 +149,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/scc/findings/list-marks b/gcloud/scc/findings/list-marks index f2925ea13..fcaafb274 100644 --- a/gcloud/scc/findings/list-marks +++ b/gcloud/scc/findings/list-marks @@ -95,9 +95,14 @@ FLAGS explicitly or let gcloud fetch one-page-at-a-time. --read-time=READ_TIME - Time used as a reference point when filtering. Absence of this field - will default to the API's version of NOW. See $ gcloud topic datetimes - for information on supported time formats. + (DEPRECATED) Time used as a reference point when filtering. Absence of + this field will default to the API's version of NOW. See $ gcloud topic + datetimes for information on supported time formats. + + The --read-time option is deprecated. For more information, [see the + deprecation notice] + (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) + on the SCC release notes page. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/scc/manage/help b/gcloud/scc/manage/help index 416aff8d8..377675eb2 100644 --- a/gcloud/scc/manage/help +++ b/gcloud/scc/manage/help @@ -18,6 +18,9 @@ GROUPS custom-modules Manage Cloud SCC (Security Command Center) custom modules. + services + Manage Cloud SCC (Security Command Center) services. + NOTES This variant is also available: diff --git a/gcloud/scc/manage/services/describe b/gcloud/scc/manage/services/describe new file mode 100644 index 000000000..bf6dd0187 --- /dev/null +++ b/gcloud/scc/manage/services/describe @@ -0,0 +1,69 @@ +NAME + gcloud scc manage services describe - get the details of a Security Command + Center service + +SYNOPSIS + gcloud scc manage services describe SERVICE_NAME + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the details of a Security Command Center service. It resolves INHERITED + enablement states to ENABLED or DISABLED for services at ancestor levels. + For example, if the service is enabled at the ancestor level, services for + all child resources will have the enablement state set to ENABLED. + +EXAMPLES + To get the details of a Security Command Center service with name sha for + organization 123, run: + + $ gcloud scc manage services describe sha --organization=123 + + To get the details of a Security Command Center service with name sha for + folder 456, run: + + $ gcloud scc manage services describe sha --folder=456 + + To get the details of a Security Command Center service with ID sha for + project 789, run: + + $ gcloud scc manage services describe sha --project=789 + + You can also specify the parent more generally: + + $ gcloud scc manage services describe sha --parent=organizations/123 + +POSITIONAL ARGUMENTS + SERVICE_NAME + The service name, provided either in lowercase hyphenated form (e.g. + security-health-analytics), or in abbreviated form (e.g. sha) + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the custom module. + + --organization=ORGANIZATION_ID + Organization associated with the custom module. + + --parent=PARENT + Parent associated with the custom module. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the custom module. + +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 variant is also available: + + $ gcloud alpha scc manage services describe + diff --git a/gcloud/scc/manage/services/help b/gcloud/scc/manage/services/help new file mode 100644 index 000000000..c6d619d82 --- /dev/null +++ b/gcloud/scc/manage/services/help @@ -0,0 +1,32 @@ +NAME + gcloud scc manage services - manage Cloud SCC (Security Command Center) + services + +SYNOPSIS + gcloud scc manage services COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud SCC (Security Command Center) services. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get the details of a Security Command Center service. + + list + List the details of Security Command Center services. + + update + Update a Security Command Center service. + +NOTES + This variant is also available: + + $ gcloud alpha scc manage services + diff --git a/gcloud/scc/manage/services/list b/gcloud/scc/manage/services/list new file mode 100644 index 000000000..642f1cea9 --- /dev/null +++ b/gcloud/scc/manage/services/list @@ -0,0 +1,88 @@ +NAME + gcloud scc manage services list - list the details of Security Command + Center services + +SYNOPSIS + gcloud scc manage services list + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the details of Security Command Center services for the specified + folder, project or organization. Services along with their corresponding + module information is returned as the response. + +EXAMPLES + To list the Security Center services for organization 123, run: + + $ gcloud scc manage services list --organization=organizations/123 + + To list Security Center services for folder 456, run: + + $ gcloud scc manage services list --folder=folders/456 + + To list Security Center services for project 789, run: + + $ gcloud scc manage services list --project=projects/789 + + You can also specify the parent more generally: + + $ gcloud scc manage services list --parent=organizations/123 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the Security Center service. + + --organization=ORGANIZATION_ID + Organization associated with the Security Center service. + + --parent=PARENT + Parent associated with the Security Center service. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the Security Center service. + +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 variant is also available: + + $ gcloud alpha scc manage services list + diff --git a/gcloud/scc/manage/services/update b/gcloud/scc/manage/services/update new file mode 100644 index 000000000..19ce23add --- /dev/null +++ b/gcloud/scc/manage/services/update @@ -0,0 +1,88 @@ +NAME + gcloud scc manage services update - update a Security Command Center + service + +SYNOPSIS + gcloud scc manage services update SERVICE_NAME + (--enablement-state=ENABLEMENT_STATE + --module-config-file=MODULE_CONFIG_FILE) + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --parent=PARENT + | --project=PROJECT_ID_OR_NUMBER) [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the enablement state of the Security Center service and its + corresponding modules for the specified folder, project or organization. + +EXAMPLES + To update a Security Center Service with name sha for organization 123, + run: + + $ gcloud scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" + + To update a Security Center Service with name sha and its modules for + organization 123, run: + + $ gcloud scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" \ + --module-config-file=module_config.yaml + + To validate an update of Security Center Service with name sha and its + modules for organization 123, run: + + $ gcloud scc manage services update sha \ + --organization=organizations/123 --enablement-state="ENABLED" \ + --module-config-file=module_config.yaml --validate-only + +POSITIONAL ARGUMENTS + SERVICE_NAME + The service name, provided either in lowercase hyphenated form (e.g. + security-health-analytics), or in abbreviated form (e.g. sha) + +REQUIRED FLAGS + At least one of these must be specified: + + --enablement-state=ENABLEMENT_STATE + Sets the enablement state of the Security Center service. Valid + options are ENABLED, DISABLED, OR INHERITED. The INHERITED state is + only valid when setting the enablement state at the project or folder + level. + + --module-config-file=MODULE_CONFIG_FILE + Path to a JSON or YAML file that contains the module config to set + for the given module and service. + + Exactly one of these must be specified: + + --folder=FOLDER_ID + Folder associated with the custom module. + + --organization=ORGANIZATION_ID + Organization associated with the custom module. + + --parent=PARENT + Parent associated with the custom module. Can be one of + organizations/, projects/, folders/ + + --project=PROJECT_ID_OR_NUMBER + Project associated with the custom module. + +OPTIONAL FLAGS + --validate-only + If present, the request is validated (including IAM checks) but no + action is taken. + +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 variant is also available: + + $ gcloud alpha scc manage services update +