imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 13:10:18 +00:00
Code Activity

gcloud: Wed Sep 14 09:28:28 UTC 2022

Browse source
This commit is contained in:
Automated 2022-09-14 09:28:28 +00:00
parent e7bec9b31b
commit 8f4214beb2
Failed to extract signature
148 changed files with 5778 additions and 334 deletions
Download patch file Download diff file Expand all files Collapse all files

6
gcloud/beta/compute/backend-services/add-iam-policy-binding
View file

@ -86,8 +86,10 @@ API REFERENCE
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute backend-services add-iam-policy-binding
$ gcloud alpha compute backend-services add-iam-policy-binding

6
gcloud/beta/compute/backend-services/get-iam-policy
View file

@ -89,8 +89,10 @@ API REFERENCE
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute backend-services get-iam-policy
$ gcloud alpha compute backend-services get-iam-policy

6
gcloud/beta/compute/backend-services/remove-iam-policy-binding
View file

@ -87,8 +87,10 @@ API REFERENCE
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute backend-services remove-iam-policy-binding
$ gcloud alpha compute backend-services remove-iam-policy-binding

6
gcloud/beta/compute/backend-services/set-iam-policy
View file

@ -68,8 +68,10 @@ API REFERENCE
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute backend-services set-iam-policy
$ gcloud alpha compute backend-services set-iam-policy

3
gcloud/beta/compute/backend-services/update
View file

@ -198,7 +198,8 @@ FLAGS
service.
--no-health-checks
Removes all health checks for the backend service.
Removes all health checks for the backend service if the backend
service has no backends attached.
--http-health-checks=HTTP_HEALTH_CHECK,[...]
Specifies a list of legacy HTTP health check objects for checking the

2
gcloud/beta/compute/instances/ops-agents/policies/create
View file

@ -95,7 +95,7 @@ REQUIRED FLAGS
The Ops Agent has both a logging module and a metrics module
already. So other types of agents are not allowed when there is an
agent with type ops-agent. See
https://cloud.google.com/stackdriver/docs/solutions/ops-agent#which_agent
https://cloud.google.com/stackdriver/docs/solutions/agents#which-agent-should-you-choose
for which agent to use.
enable-autoupgrade

2
gcloud/beta/compute/instances/ops-agents/policies/update
View file

@ -117,7 +117,7 @@ FLAGS
The Ops Agent has both a logging module and a metrics module
already. So other types of agents are not allowed when there is an
agent with type ops-agent. See
https://cloud.google.com/stackdriver/docs/solutions/ops-agent#which_agent
https://cloud.google.com/stackdriver/docs/solutions/agents#which-agent-should-you-choose
for which agent to use.
enable-autoupgrade

144
gcloud/beta/compute/security-policies/rules/add-preconfig-waf-exclusion Normal file
View file

@ -0,0 +1,144 @@
NAME
gcloud beta compute security-policies rules add-preconfig-waf-exclusion -
add an exclusion configuration for preconfigured WAF evaluation into a
security policy rule
SYNOPSIS
gcloud beta compute security-policies rules add-preconfig-waf-exclusion
PRIORITY --target-rule-set=TARGET_RULE_SET
[--request-cookie-to-exclude=[op=OP],[val=VAL]]
[--request-header-to-exclude=[op=OP],[val=VAL]]
[--request-query-param-to-exclude=[op=OP],[val=VAL]]
[--request-uri-to-exclude=[op=OP],[val=VAL]]
[--security-policy=SECURITY_POLICY] [--target-rule-ids=[RULE_ID,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute security-policies rules
add-preconfig-waf-exclusion is used to add an exclusion configuration for
preconfigured WAF evaluation into a security policy rule.
Note that request field exclusions are associated with a target, which can
be a single rule set, or a rule set plus a list of rule IDs under the rule
set.
EXAMPLES
To add specific request field exclusions that are associated with the
target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli',
'owasp-crs-v030001-id942120-sqli'], run:
$ gcloud beta compute security-policies rules \
add-preconfig-waf-exclusion 1000 --security-policy=my-policy \
--target-rule-set=sqli-stable \
--target-rule-ids=owasp-crs-v030001-id942110-sqli,\
owasp-crs-v030001-id942120-sqli \
--request-header-to-exclude=op=EQUALS,val=abc \
--request-header-to-exclude=op=STARTS_WITH,val=xyz \
--request-uri-to-exclude=op=EQUALS_ANY
To add specific request field exclusions that are associated with the
target of 'sqli-stable': [], run:
$ gcloud beta compute security-policies rules \
add-preconfig-waf-exclusion 1000 --security-policy=my-policy \
--target-rule-set=sqli-stable \
--request-cookie-to-exclude=op=EQUALS_ANY
POSITIONAL ARGUMENTS
PRIORITY
The priority of the rule to add the exclusion configuration for
preconfigured WAF evaluation. Rules are evaluated in order from highest
priority to lowest priority where 0 is the highest priority and
2147483647 is the lowest priority.
REQUIRED FLAGS
--target-rule-set=TARGET_RULE_SET
Target WAF rule set where the request field exclusions being added
would apply.
This, together with the target rule IDs (if given), determines the
target for associating request field exclusions. See --target-rule-ids.
OPTIONAL FLAGS
--request-cookie-to-exclude=[op=OP],[val=VAL]
Adds a request cookie to the request field exclusions associated with
the rule set and rule IDs (if given). This specifies a request cookie
whose value will be excluded from inspection during preconfigured WAF
evaluation.
You can specify an exact match or a partial match by using a field
operator and a field value. Available field operators are:
◆ EQUALS: the operator matches if the field value equals the
specified value.
◆ STARTS_WITH: the operator matches if the field value starts with
the specified value.
◆ ENDS_WITH: the operator matches if the field value ends with the
specified value.
◆ CONTAINS: the operator matches if the field value contains the
specified value.
◆ EQUALS_ANY: the operator matches if the field value is any value.
A field value must be given if the field operator is not EQUALS_ANY,
and cannot be given if the field operator is EQUALS_ANY. For example,
--request-header-to-exclude op=EQUALS,val=abc or
--request-header-to-exclude op=EQUALS_ANY.
This flag can be repeated to specify multiple request headers to
exclude. For example, --request-header-to-exclude op=EQUALS,val=abc
--request-header-to-exclude op=STARTS_WITH,val=xyz.
--request-header-to-exclude=[op=OP],[val=VAL]
Adds a request header to the request field exclusions associated with
the rule set and rule IDs (if given). This specifies a request header
whose value will be excluded from inspection during preconfigured WAF
evaluation.
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request headers.
--request-query-param-to-exclude=[op=OP],[val=VAL]
Adds a request query parameter to the request field exclusions
associated with the rule set and rule IDs (if given). This specifies a
request query parameter in the query string or in the POST body whose
value will be excluded from inspection during preconfigured WAF
evaluation.
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request query parameters.
--request-uri-to-exclude=[op=OP],[val=VAL]
Adds a request URI to the request field exclusions associated with the
rule set and rule IDs (if given). This specifies a request URI from the
request line to be excluded from inspection during preconfigured WAF
evaluation.
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request URIs.
--security-policy=SECURITY_POLICY
The security policy that this rule belongs to.
--target-rule-ids=[RULE_ID,...]
A comma-separated list of target rule IDs under the WAF rule set where
the request field exclusions being added would apply. If omitted, the
added request field exclusions will be associated with the rule set
only, which would apply to all the rule IDs under the rule set.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute security-policies rules \
add-preconfig-waf-exclusion

8
gcloud/beta/compute/security-policies/rules/help
View file

@ -16,6 +16,10 @@ GCLOUD WIDE FLAGS
COMMANDS
COMMAND is one of the following:
add-preconfig-waf-exclusion
(BETA) Add an exclusion configuration for preconfigured WAF evaluation
into a security policy rule.
create
(BETA) Create a Compute Engine security policy rule.
@ -25,6 +29,10 @@ COMMANDS
describe
(BETA) Describe a Compute Engine security policy rule.
remove-preconfig-waf-exclusion
(BETA) Remove an exclusion configuration for preconfigured WAF
evaluation from a security policy rule.
update
(BETA) Update a Compute Engine security policy rule.

162
gcloud/beta/compute/security-policies/rules/remove-preconfig-waf-exclusion Normal file
View file

@ -0,0 +1,162 @@
NAME
gcloud beta compute security-policies rules remove-preconfig-waf-exclusion
- remove an exclusion configuration for preconfigured WAF evaluation
from a security policy rule
SYNOPSIS
gcloud beta compute security-policies rules remove-preconfig-waf-exclusion
PRIORITY --target-rule-set=TARGET_RULE_SET
[--request-cookie-to-exclude=[op=OP],[val=VAL]]
[--request-header-to-exclude=[op=OP],[val=VAL]]
[--request-query-param-to-exclude=[op=OP],[val=VAL]]
[--request-uri-to-exclude=[op=OP],[val=VAL]]
[--security-policy=SECURITY_POLICY] [--target-rule-ids=[RULE_ID,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute security-policies rules
remove-preconfig-waf-exclusion is used to remove an exclusion configuration
for preconfigured WAF evaluation from a security policy rule.
Note that request field exclusions are associated with a target, which can
be a single rule set, or a rule set plus a list of rule IDs under the rule
set.
It is possible to remove request field exclusions at 3 levels:
▪ Remove specific request field exclusions that are associated with a
matching target.
▪ Remove all the request field exclusions that are associated with a
matching target.
▪ Remove all the request field exclusions that are configured under the
security policy rule, regardless of the target.
EXAMPLES
To remove specific request field exclusions that are associated with the
target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli',
'owasp-crs-v030001-id942120-sqli'], run:
$ gcloud beta compute security-policies rules \
remove-preconfig-waf-exclusion 1000 \
--security-policy=my-policy --target-rule-set=sqli-stable \
--target-rule-ids=owasp-crs-v030001-id942110-sqli,\
owasp-crs-v030001-id942120-sqli \
--request-header-to-exclude=op=EQUALS,val=abc \
--request-header-to-exclude=op=STARTS_WITH,val=xyz \
--request-uri-to-exclude=op=EQUALS_ANY
To remove all the request field exclusions that are associated with the
target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli',
'owasp-crs-v030001-id942120-sqli'], run:
$ gcloud beta compute security-policies rules \
remove-preconfig-waf-exclusion 1000 \
--security-policy=my-policy --target-rule-set=sqli-stable \
--target-rule-ids=owasp-crs-v030001-id942110-sqli,\
owasp-crs-v030001-id942120-sqli
To remove all the request field exclusions that are associated with the
target of 'sqli-stable': [], run:
$ gcloud beta compute security-policies rules \
remove-preconfig-waf-exclusion 1000 \
--security-policy=my-policy --target-rule-set=sqli-stable
To remove all the request field exclusions that are configured under the
security policy rule, regardless of the target, run:
$ gcloud beta compute security-policies rules \
remove-preconfig-waf-exclusion 1000 \
--security-policy=my-policy --target-rule-set=*
POSITIONAL ARGUMENTS
PRIORITY
The priority of the rule to remove the exclusion configuration for
preconfigured WAF evaluation. Rules are evaluated in order from highest
priority to lowest priority where 0 is the highest priority and
2147483647 is the lowest priority.
REQUIRED FLAGS
--target-rule-set=TARGET_RULE_SET
Target WAF rule set from where to remove the request field exclusions.
This, together with the target rule IDs (if given), determines the
target for associating request field exclusions. See --target-rule-ids.
Note that the removal of request field exclusions is restricted to
those associated with a matching target. Set this flag to * if you want
to remove request field exclusions regardless of the target.
OPTIONAL FLAGS
--request-cookie-to-exclude=[op=OP],[val=VAL]
Removes a request cookie from the existing request field exclusions
associated with the rule set and rule IDs (if given).
You can specify an exact match or a partial match by using a field
operator and a field value. Available field operators are:
◆ EQUALS: the operator matches if the field value equals the
specified value.
◆ STARTS_WITH: the operator matches if the field value starts with
the specified value.
◆ ENDS_WITH: the operator matches if the field value ends with the
specified value.
◆ CONTAINS: the operator matches if the field value contains the
specified value.
◆ EQUALS_ANY: the operator matches if the field value is any value.
A field value must be given if the field operator is not EQUALS_ANY,
and cannot be given if the field operator is EQUALS_ANY. For example,
--request-header-to-exclude op=EQUALS,val=abc or
--request-header-to-exclude op=EQUALS_ANY.
This flag can be repeated to specify multiple request headers to
exclude. For example, --request-header-to-exclude op=EQUALS,val=abc
--request-header-to-exclude op=STARTS_WITH,val=xyz.
--request-header-to-exclude=[op=OP],[val=VAL]
Removes a request header from the existing request field exclusions
associated with the rule set and rule IDs (if given).
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request headers.
--request-query-param-to-exclude=[op=OP],[val=VAL]
Removes a request query parameter from the existing request field
exclusions associated with the rule set and rule IDs (if given).
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request query parameters.
--request-uri-to-exclude=[op=OP],[val=VAL]
Removes a request URI from the existing request field exclusions
associated with the rule set and rule IDs (if given).
Refer to the syntax under --request-cookie-to-exclude.
This flag can be repeated to specify multiple request URIs.
--security-policy=SECURITY_POLICY
The security policy that this rule belongs to.
--target-rule-ids=[RULE_ID,...]
A comma-separated list of target rule IDs under the WAF rule set from
where to remove the request field exclusions. If omitted, the removal
of request field exclusions is restricted to those associated with the
rule set only, without specific rule IDs.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute security-policies rules \
remove-preconfig-waf-exclusion