gcloud: Wed Oct 25 11:42:23 UTC 2023

gcloud/ai/index-endpoints/create

@@ -3,9 +3,11 @@ NAME
 
 SYNOPSIS
     gcloud ai index-endpoints create --display-name=DISPLAY_NAME
-        [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
-        [--network=NETWORK] [--public-endpoint-enabled] [--region=REGION]
-        [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [--enable-private-service-connect]
+        [--encryption-kms-key-name=ENCRYPTION_KMS_KEY_NAME]
+        [--labels=[KEY=VALUE,...]] [--network=NETWORK]
+        [--project-allowlist=[PROJECTS,...]] [--public-endpoint-enabled]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
 
 EXAMPLES
     To create an index endpoint under project example with network
@@ -24,6 +26,17 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the index endpoint.
 
+     --enable-private-service-connect
+        If true, expose the index endpoint via private service connect.
+
+     --encryption-kms-key-name=ENCRYPTION_KMS_KEY_NAME
+        The Cloud KMS resource identifier of the customer managed encryption
+        key used to protect a resource. Has the form:
+        projects/my-project/locations/my-region/keyRings/my-kr/cryptoKeys/my-key.
+
+        The key needs to be in the same region as where the compute resource is
+        created.
+
      --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.
 
@@ -36,6 +49,10 @@ OPTIONAL FLAGS
         The Google Compute Engine network name to which the IndexEndpoint
         should be peered.
 
+     --project-allowlist=[PROJECTS,...]
+        List of projects from which the forwarding rule will target the service
+        attachment.
+
      --public-endpoint-enabled
         If true, the deployed index will be accessible through public endpoint.
 

gcloud/ai/index-endpoints/deploy-index

@@ -5,7 +5,9 @@ NAME
 SYNOPSIS
     gcloud ai index-endpoints deploy-index (INDEX_ENDPOINT : --region=REGION)
         --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME
-        --index=INDEX [--machine-type=MACHINE_TYPE]
+        --index=INDEX [--allowed-issuers=[ALLOWED_ISSUERS,...]]
+        [--audiences=[AUDIENCES,...]] [--deployment-group=DEPLOYMENT_GROUP]
+        [--enable-access-logging] [--machine-type=MACHINE_TYPE]
         [--max-replica-count=MAX_REPLICA_COUNT]
         [--min-replica-count=MIN_REPLICA_COUNT]
         [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...]
@@ -16,14 +18,14 @@ DESCRIPTION
 EXAMPLES
     To deploy index 345 to an index endpoint 456 with 2 min replica count and
     10 max replica count under project example in region us-central1, within
-    reserved ip ranges vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 run:
+    reserved ip ranges vertex-ai-ip-range-1 and vertex-ai-ip-range-2 run:
 
         $ gcloud ai index-endpoints deploy-index 456 --project=example \
             --region=us-central1 --index=345 \
             --deployed-index-id=deployed-index-345 \
             --display-name=deployed-index-345 --min-replica-count=2 \
             --max-replica-count=10 \
-            --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2
+            --reserved-ip-ranges=vertex-ai-ip-range-1,vertex-ai-ip-range-2
 
 POSITIONAL ARGUMENTS
      Index endpoint resource - The index endpoint to deploy an index. The
@@ -70,6 +72,34 @@ REQUIRED FLAGS
         ID of the index.
 
 OPTIONAL FLAGS
+     --allowed-issuers=[ALLOWED_ISSUERS,...]
+        List of allowed JWT issuers for a deployed index.
+
+        Each entry must be a valid Google service account, in the following
+        format: service-account-name@project-id.iam.gserviceaccount.com
+
+     --audiences=[AUDIENCES,...]
+        List of JWT audiences that are allowed to access a deployed index.
+
+        JWT containing any of these audiences
+        (https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section
+        -4.1.3) will be accepted.
+
+     --deployment-group=DEPLOYMENT_GROUP
+        Deployment group can be no longer than 64 characters (eg:test, prod).
+        If not set, we will use the default deployment group.
+
+        Creating deployment_groups with reserved_ip_ranges is a recommended
+        practice when the peered network has multiple peering ranges.This
+        creates your deployments from predictable IP spaces for easier traffic
+        administration.
+
+     --enable-access-logging
+        If true, online prediction access logs are sent to Cloud Logging.
+
+        These logs are standard server access logs, containing information like
+        timestamp and latency for each prediction request.
+
      --machine-type=MACHINE_TYPE
         The machine resources to be used for each node of this deployment. For
         available machine types, see

gcloud/ai/indexes/create

@@ -4,8 +4,9 @@ NAME
 SYNOPSIS
     gcloud ai indexes create --display-name=DISPLAY_NAME
         --metadata-file=METADATA_FILE [--description=DESCRIPTION]
-        [--labels=[KEY=VALUE,...]] [--metadata-schema-uri=METADATA_SCHEMA_URI]
-        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+        [--index-update-method=INDEX_UPDATE_METHOD] [--labels=[KEY=VALUE,...]]
+        [--metadata-schema-uri=METADATA_SCHEMA_URI] [--region=REGION]
+        [GCLOUD_WIDE_FLAG ...]
 
 EXAMPLES
     To create an index under project example in region us-central1, run:
@@ -26,6 +27,16 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         Description of the index.
 
+     --index-update-method=INDEX_UPDATE_METHOD
+        The update method to use with this index. Choose stream_update or
+        batch_update. If not set, batch update will be used by default.
+
+        batch_update: can update index with gcloud ai indexes update using
+        datapoints files on Cloud Storage.
+
+        stream update: can update datapoints with upsert-datapoints and
+        delete-datapoints and will be applied nearly real-time.
+
      --labels=[KEY=VALUE,...]
         List of label KEY=VALUE pairs to add.