imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00
Code Activity

gcloud: Thu Nov 9 11:45:52 UTC 2023

Browse source
This commit is contained in:
Automated 2023-11-09 11:45:52 +00:00
parent f2c5d1d45f
commit 03f0979970
300 changed files with 8569 additions and 1319 deletions
Download patch file Download diff file Expand all files Collapse all files

40
gcloud/ai/index-endpoints/mutate-deployed-index
View file

@ -6,6 +6,8 @@ SYNOPSIS
gcloud ai index-endpoints mutate-deployed-index
(INDEX_ENDPOINT : --region=REGION)
--deployed-index-id=DEPLOYED_INDEX_ID
[--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]]
[--deployment-group=DEPLOYMENT_GROUP] [--enable-access-logging]
[--max-replica-count=MAX_REPLICA_COUNT]
[--min-replica-count=MIN_REPLICA_COUNT]
[--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...]
@ -16,14 +18,18 @@ DESCRIPTION
EXAMPLES
To mutated a deployed index deployed-index-123 from an index endpoint 456
with 2 min replica count and 10 max replica count under project example in
region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2
run:
region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2,
within deployment group test, enabling access logging, with JWT audiences
aud1 and aud2, JWT issuers issuer1 and issuer2 run:
$ gcloud ai index-endpoints mutate-deployed-index 456 \
--project=example --region=us-central1 \
--deployed-index-id=deployed-index-123 --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-ranges-1,\
vertex-ai-ip-ranges-2 --enable-access-logging \
--audiences=aud1,aud2 --allowed-issuers=issuer1,issuer2 \
--deployment-group=test
POSITIONAL ARGUMENTS
Index endpoint resource - The index endpoint ID of the index endpoint..
@ -64,6 +70,34 @@ REQUIRED FLAGS
Id of the deployed 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.
--max-replica-count=MAX_REPLICA_COUNT
Maximum number of machine replicas the deployed index will be always
deployed on.