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

gcloud: Wed Mar 5 10:41:25 UTC 2025

This commit is contained in:
Automated 2025-03-05 10:41:25 +00:00
parent a597993b2e
commit 6dc93282df
279 changed files with 4198 additions and 801 deletions

View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud alpha metastore services create (SERVICE : --location=LOCATION)
[--async] [--autoscaling-enabled] [--data-catalog-sync]
[--database-type=DATABASE_TYPE; default="mysql"]
[--deletion-protection] [--encryption-kms-key=ENCRYPTION_KMS_KEY]
[--deletion-protection]
[--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"]
[--hive-metastore-version=HIVE_METASTORE_VERSION]
[--labels=[KEY=VALUE,...]] [--port=PORT; default=9083]
@ -15,6 +15,8 @@ SYNOPSIS
| --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE]
[--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK
| --network-config-from-file=NETWORK_CONFIG_FROM_FILE]
[--encryption-kms-key=ENCRYPTION_KMS_KEY
| --encryption-kms-keys=[ENCRYPTION_KMS_KEYS,...]]
[--hive-metastore-configs=[KEY=VALUE,...]
| --hive-metastore-configs-from-file=PATH_TO_FILE]
[--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR
@ -125,13 +127,6 @@ FLAGS
prevent accidental deletions of the instance. Use --deletion-protection
to enable.
--encryption-kms-key=ENCRYPTION_KMS_KEY
The name of the Cloud KMS key to use for customer data encryption.
Cannot be changed once the service is created. Mutually exclusive with
flag --data-catalog-sync. This can be provided as a fully-qualified
URL, or a relative name in the form
projects/{project_id}/locations/{location}/keyRings/{key_ring_id}/cryptoKeys/{crypto_key_id}.
--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"
The protocol to use for the metastore service endpoint. If unspecified,
defaults to THRIFT. ENDPOINT_PROTOCOL must be one of:
@ -243,6 +238,25 @@ FLAGS
projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}
...
Encryption configuration for the metastore service.
At most one of these can be specified:
--encryption-kms-key=ENCRYPTION_KMS_KEY
The name of the Cloud KMS key to use for customer data encryption.
Cannot be changed once the service is created. Mutually exclusive
with flag --data-catalog-sync. This can be provided as a
fully-qualified URL, or a relative name in the form
projects/{project_id}/locations/{location}/keyRings/{key_ring_id}/cryptoKeys/{crypto_key_id}.
--encryption-kms-keys=[ENCRYPTION_KMS_KEYS,...]
Comma-separated list of the Cloud KMS keys to use for customer data
encryption. Cannot be changed once the service is created. Mutually
exclusive with flag --data-catalog-sync and --encryption-kms-key.
Each key can be provided as a fully-qualified URL, or a relative name
in the form
projects/{project_id}/locations/{location}/keyRings/{key_ring_id}/cryptoKeys/{crypto_key_id}.
Configuration properties specific to running Hive metastore software as
the metastore service.