mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 10:35:03 +00:00
gcloud: Wed Feb 7 10:26:58 UTC 2024
This commit is contained in:
parent
40bc27506b
commit
3efce28165
109 changed files with 4100 additions and 399 deletions
|
|
@ -8,7 +8,8 @@ SYNOPSIS
|
|||
[--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION]
|
||||
[--split-source-commitment=SPLIT_SOURCE_COMMITMENT]
|
||||
[--type=TYPE; default="general-purpose"]
|
||||
[--reservations-from-file=RESERVATIONS_FROM_FILE
|
||||
[--existing-reservation=[name=NAME],[zone=ZONE]
|
||||
| --reservations-from-file=RESERVATIONS_FROM_FILE
|
||||
| [--reservation=RESERVATION : --reservation-zone=RESERVATION_ZONE
|
||||
--accelerator=[count=COUNT],[type=TYPE]
|
||||
--local-ssd=[interface=INTERFACE],[size=SIZE]
|
||||
|
|
@ -106,6 +107,20 @@ OPTIONAL FLAGS
|
|||
|
||||
At most one of these can be specified:
|
||||
|
||||
--existing-reservation=[name=NAME],[zone=ZONE]
|
||||
Details of the existing on-demand reservation or auto-created future
|
||||
reservation that you want to attach to your commitment. Specify a new
|
||||
instance of this flag for every existing reservation that you want to
|
||||
attach. The reservations must be in the same region as the
|
||||
commitment.
|
||||
name
|
||||
The name of the reservation.
|
||||
zone
|
||||
The zone of the reservation. For example, to attach an existing
|
||||
reservation named reservation-name in the zone reservation-zone,
|
||||
use the following text:
|
||||
--existing-reservation=name=reservation-name,zone=reservation-zone
|
||||
|
||||
--reservations-from-file=RESERVATIONS_FROM_FILE
|
||||
Path to a YAML file of multiple reservations' configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,6 +30,9 @@ GROUPS
|
|||
network-interfaces
|
||||
Read and manipulate Compute Engine VM instance network interfaces.
|
||||
|
||||
ops-agents
|
||||
Manage Operation Suite (Ops) agents for Compute Engine VM instances.
|
||||
|
||||
os-inventory
|
||||
Read Compute Engine OS Inventory Data and Related Resources.
|
||||
|
||||
|
|
|
|||
29
gcloud/compute/instances/ops-agents/help
Normal file
29
gcloud/compute/instances/ops-agents/help
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
NAME
|
||||
gcloud compute instances ops-agents - manage Operation Suite (Ops) agents
|
||||
for Compute Engine VM instances
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute instances ops-agents GROUP [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Manage Operation Suite (Ops) agents for Compute Engine VM instances.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --help.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
GROUPS
|
||||
GROUP is one of the following:
|
||||
|
||||
policies
|
||||
Manage Operation Suite (Ops) agents policies that install, update, and
|
||||
uninstall agents for Compute Engine VM instances.
|
||||
|
||||
NOTES
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute instances ops-agents
|
||||
|
||||
$ gcloud beta compute instances ops-agents
|
||||
|
||||
24
gcloud/compute/instances/ops-agents/policies/help
Normal file
24
gcloud/compute/instances/ops-agents/policies/help
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
NAME
|
||||
gcloud compute instances ops-agents policies - manage Operation Suite (Ops)
|
||||
agents policies that install, update, and uninstall agents for Compute
|
||||
Engine VM instances
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute instances ops-agents policies COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Manage Operation Suite (Ops) agents policies that install, update, and
|
||||
uninstall agents for Compute Engine VM instances.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --help.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
NOTES
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha compute instances ops-agents policies
|
||||
|
||||
$ gcloud beta compute instances ops-agents policies
|
||||
|
||||
|
|
@ -17,7 +17,7 @@ DESCRIPTION
|
|||
is used to add layer7 ddos defense threshold configs to security policies.
|
||||
|
||||
EXAMPLES
|
||||
To add a layer7 ddos defense threshold config run the following command:
|
||||
To add a layer7 ddos defense threshold config, run the following command:
|
||||
|
||||
$ gcloud compute security-policies \
|
||||
add-layer7-ddos-defense-threshold-config NAME \
|
||||
|
|
@ -37,7 +37,7 @@ REQUIRED FLAGS
|
|||
|
||||
OPTIONAL FLAGS
|
||||
--auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD
|
||||
The threshold of the confidence of an identified attack over which
|
||||
The threshold of the confidence of an identified attack, over which
|
||||
auto-deploy takes action.
|
||||
|
||||
--auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC
|
||||
|
|
@ -48,7 +48,7 @@ OPTIONAL FLAGS
|
|||
suggested mitigation, below which auto-deploy takes action.
|
||||
|
||||
--auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD
|
||||
The threshold on backend's load over which auto-deploy takes action.
|
||||
The threshold on backend's load, over which auto-deploy takes action.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue