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

gcloud: Wed Sep 25 09:51:52 UTC 2024

This commit is contained in:
Automated 2024-09-25 09:51:52 +00:00
parent 8ebed5b0f1
commit 0a5b6f11af
202 changed files with 9781 additions and 830 deletions

View file

@ -93,23 +93,23 @@ FLAGS
Data Boost Read-only Isolation
--data-boost
Use Data Boost Read-only Isolation, rather than Standard Isolation.
If specified, --data-boost-compute-billing-owner is required.
Specifying Data Boost Read-only Isolation on an app profile which
has Standard Isolation enabled may cause unexpected behavior for
running applications.
Use Data Boost serverless compute option, rather than standard
provisioned node compute. If specified,
--data-boost-compute-billing-owner is required. Specifying Data
Boost compute on an app profile that uses standard provisioned node
compute may cause unexpected behavior for running applications.
This flag argument must be specified if any of the other arguments
in this group are specified.
--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER
Specify the Data Boost Compute Billing Owner, required if
Specify the Data Boost compute billing owner, required if
--data-boost is passed. DATA_BOOST_COMPUTE_BILLING_OWNER must be
(only one value is supported):
HOST_PAYS
Compute Billing should be accounted towards the host Cloud
Project (containing the targeted Bigtable Instance / Table).
Compute billing should be accounted towards the host Cloud
project (containing the targeted Bigtable instance / table).
This flag argument must be specified if any of the other arguments
in this group are specified.
@ -117,14 +117,15 @@ FLAGS
Standard Isolation
--priority=PRIORITY
Specify the request priority under Standard Isolation. Passing this
option implies Standard Isolation, e.g. the --standard option. If
not specified, the app profile uses Standard Isolation with
PRIORITY_HIGH by default. Specifying request priority on an app
profile that has Data Boost Read-Only Isolation enabled will change
the isolation to Standard and use the specified priority, which may
cause unexpected behavior for running applications. PRIORITY must
be one of:
Specify the request priority under standard provisioned node
compute capabilities. Passing this option implies standard
provisioned node compute, e.g. the --standard option. If not
specified, the app profile uses standard provisioned node compute
with PRIORITY_HIGH by default. Specifying request priority on an
app profile that has Data Boost serverless compute enabled changes
the compute option to standard and uses the specified priority,
which might cause unexpected behavior for running applications.
PRIORITY must be one of:
PRIORITY_HIGH
Requests are treated with high priority.
@ -137,8 +138,8 @@ FLAGS
in this group are specified.
--standard
Use Standard Isolation, rather than Data Boost Read-only Isolation.
If specified, --priority is required.
Use standard provisioned node compute option, rather than Data
Boost compute option. If specified, --priority is required.
At most one of these can be specified: