imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-21 06:27:15 +00:00
Code Activity

gcloud: Wed Oct 16 09:53:34 UTC 2024

Browse source
This commit is contained in:
Automated 2024-10-16 09:53:35 +00:00
parent 4ffb04ab9e
commit 694f6671d0
151 changed files with 4031 additions and 414 deletions
Download patch file Download diff file Expand all files Collapse all files

73
gcloud/bigtable/app-profiles/create
View file

@ -5,10 +5,8 @@ SYNOPSIS
gcloud bigtable app-profiles create (APP_PROFILE : --instance=INSTANCE)
([--route-any : --restrict-to=[RESTRICT_TO,...]]
| [--route-to=ROUTE_TO : --transactional-writes])
[--description=DESCRIPTION] [--force]
[--data-boost
--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER
| [--priority=PRIORITY : --standard]] [GCLOUD_WIDE_FLAG ...]
[--description=DESCRIPTION] [--force] [--priority=PRIORITY]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create a new Bigtable app profile.
@ -37,13 +35,6 @@ EXAMPLES
$ gcloud bigtable app-profiles create my-app-profile-id \
--instance=my-instance-id --route-any --priority=PRIORITY_MEDIUM
To create an app profile with Data Boost enabled which bills usage to the
host project, run:
$ gcloud bigtable app-profiles create my-app-profile-id \
--instance=my-instance-id --data-boost \
--data-boost-compute-billing-owner=HOST_PAYS
POSITIONAL ARGUMENTS
App profile resource - The app profile to create. The arguments in this
group can be used to specify the attributes of this resource. (NOTE) Some
@ -109,58 +100,16 @@ OPTIONAL FLAGS
--force
Ignore warnings and force create.
At most one of these can be specified:
--priority=PRIORITY
Specify the request priority. If not specified, the app profile uses
PRIORITY_HIGH by default. PRIORITY must be one of:
Data Boost Read-only Isolation
--data-boost
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
--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).
This flag argument must be specified if any of the other arguments
in this group are specified.
Standard Isolation
--priority=PRIORITY
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.
PRIORITY_LOW
Requests are treated with low priority.
PRIORITY_MEDIUM
Requests are treated with medium priority.
This flag argument must be specified if any of the other arguments
in this group are specified.
--standard
Use standard provisioned node compute option, rather than Data
Boost compute option. If specified, --priority is required.
PRIORITY_HIGH
Requests are treated with high priority.
PRIORITY_LOW
Requests are treated with low priority.
PRIORITY_MEDIUM
Requests are treated with medium priority.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

72
gcloud/bigtable/app-profiles/update
View file

@ -3,10 +3,7 @@ NAME
SYNOPSIS
gcloud bigtable app-profiles update (APP_PROFILE : --instance=INSTANCE)
[--async] [--description=DESCRIPTION] [--force]
[--data-boost
--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER
| [--priority=PRIORITY : --standard]]
[--async] [--description=DESCRIPTION] [--force] [--priority=PRIORITY]
[[--route-any : --restrict-to=[RESTRICT_TO,...]]
| [--route-to=ROUTE_TO : --transactional-writes]]
[GCLOUD_WIDE_FLAG ...]
@ -37,13 +34,6 @@ EXAMPLES
$ gcloud bigtable app-profiles update my-app-profile-id \
--instance=my-instance-id --priority=PRIORITY_LOW
To update an app profile to enable Data Boost which bills usage to the host
project, run:
$ gcloud bigtable app-profiles update my-app-profile-id \
--instance=my-instance-id --data-boost \
--data-boost-compute-billing-owner=HOST_PAYS
POSITIONAL ARGUMENTS
App profile resource - The app profile to update. The arguments in this
group can be used to specify the attributes of this resource. (NOTE) Some
@ -87,58 +77,16 @@ FLAGS
--force
Ignore warnings and force update.
At most one of these can be specified:
--priority=PRIORITY
Specify the request priority. If not specified, the app profile uses
PRIORITY_HIGH by default. PRIORITY must be one of:
Data Boost Read-only Isolation
--data-boost
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
--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).
This flag argument must be specified if any of the other arguments
in this group are specified.
Standard Isolation
--priority=PRIORITY
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.
PRIORITY_LOW
Requests are treated with low priority.
PRIORITY_MEDIUM
Requests are treated with medium priority.
This flag argument must be specified if any of the other arguments
in this group are specified.
--standard
Use standard provisioned node compute option, rather than Data
Boost compute option. If specified, --priority is required.
PRIORITY_HIGH
Requests are treated with high priority.
PRIORITY_LOW
Requests are treated with low priority.
PRIORITY_MEDIUM
Requests are treated with medium priority.
At most one of these can be specified: