mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Aug 13 10:57:55 UTC 2025
This commit is contained in:
parent
4f9f745739
commit
d6d01162c7
357 changed files with 4606 additions and 9471 deletions
|
|
@ -9,7 +9,8 @@ SYNOPSIS
|
|||
[--egress-policies=YAML_FILE] [--ingress-policies=YAML_FILE]
|
||||
[--perimeter-type=PERIMETER_TYPE; default="regular"]
|
||||
[--resources=[RESOURCES,...]] [--restricted-services=[SERVICE,...]]
|
||||
[--enable-vpc-accessible-services
|
||||
[--vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
| --enable-vpc-accessible-services
|
||||
--vpc-allowed-services=[VPC_SERVICE,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -112,14 +113,28 @@ OPTIONAL FLAGS
|
|||
Comma-separated list of services to which the perimeter boundary does
|
||||
apply (for example, storage.googleapis.com).
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in the
|
||||
vpc-allowed-services list.
|
||||
At most one of these can be specified:
|
||||
|
||||
--vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use reference
|
||||
"RESTRICTED-SERVICES". Requires vpc-accessible-services be enabled.
|
||||
--vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
Path to a YAML file containing the full VPC Accessible Services
|
||||
configuration. This file should contain a single YAML object
|
||||
representing a VpcAccessibleServices message as described in the API
|
||||
reference. This cannot be used with --vpc-allowed-services or
|
||||
--enable-vpc-accessible-services.
|
||||
|
||||
For more information about the alpha version, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1alpha/accessPolicies.servicePerimeters
|
||||
For more information about non-alpha versions, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1/accessPolicies.servicePerimeters
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in the
|
||||
vpc-allowed-services list.
|
||||
|
||||
--vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use reference
|
||||
"RESTRICTED-SERVICES". Requires vpc-accessible-services be enabled.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
|
|
@ -8,7 +8,8 @@ SYNOPSIS
|
|||
(--access-levels=[access_levels,...] --egress-policies=YAML_FILE
|
||||
--ingress-policies=YAML_FILE --resources=[resources,...]
|
||||
--restricted-services=[restricted_services,...]
|
||||
--enable-vpc-accessible-services
|
||||
--vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
| --enable-vpc-accessible-services
|
||||
--vpc-allowed-services=[vpc_allowed_services,...]
|
||||
| [--perimeter-title=PERIMETER_TITLE --perimeter-type=PERIMETER_TYPE
|
||||
: --perimeter-access-levels=[access_levels,...]
|
||||
|
|
@ -17,7 +18,8 @@ SYNOPSIS
|
|||
--perimeter-ingress-policies=YAML_FILE
|
||||
--perimeter-resources=[resources,...]
|
||||
--perimeter-restricted-services=[restricted_services,...]
|
||||
--perimeter-enable-vpc-accessible-services
|
||||
--perimeter-vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
| --perimeter-enable-vpc-accessible-services
|
||||
--perimeter-vpc-allowed-services=[vpc_allowed_services,...]])
|
||||
[--async] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -112,15 +114,20 @@ REQUIRED FLAGS
|
|||
Comma-separated list of services to which the perimeter boundary
|
||||
does apply (for example, storage.googleapis.com).
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in the
|
||||
vpc-allowed-services list.
|
||||
At most one of these can be specified:
|
||||
|
||||
--vpc-allowed-services=[vpc_allowed_services,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use
|
||||
reference "RESTRICTED-SERVICES". Requires vpc-accessible-services
|
||||
be enabled.
|
||||
--vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
Path to a YAML file containing a VpcAccessibleServices object.
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in
|
||||
the vpc-allowed-services list.
|
||||
|
||||
--vpc-allowed-services=[vpc_allowed_services,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use
|
||||
reference "RESTRICTED-SERVICES". Requires vpc-accessible-services
|
||||
be enabled.
|
||||
|
||||
Arguments for creating a dry-run spec for a new Service Perimeter.
|
||||
|
||||
|
|
@ -180,15 +187,20 @@ REQUIRED FLAGS
|
|||
Comma-separated list of services to which the perimeter boundary
|
||||
does apply (for example, storage.googleapis.com).
|
||||
|
||||
--perimeter-enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in the
|
||||
vpc-allowed-services list.
|
||||
At most one of these can be specified:
|
||||
|
||||
--perimeter-vpc-allowed-services=[vpc_allowed_services,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use
|
||||
reference "RESTRICTED-SERVICES". Requires vpc-accessible-services
|
||||
be enabled.
|
||||
--perimeter-vpc-accessible-services=VPC_ACCESSIBLE_SERVICES_YAML_FILE
|
||||
Path to a YAML file containing a VpcAccessibleServices object.
|
||||
|
||||
--perimeter-enable-vpc-accessible-services
|
||||
Whether to restrict API calls within the perimeter to those in
|
||||
the vpc-allowed-services list.
|
||||
|
||||
--perimeter-vpc-allowed-services=[vpc_allowed_services,...]
|
||||
Comma-separated list of APIs accessible from within the Service
|
||||
Perimeter. In order to include all restricted services, use
|
||||
reference "RESTRICTED-SERVICES". Requires vpc-accessible-services
|
||||
be enabled.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--async
|
||||
|
|
|
|||
|
|
@ -14,10 +14,12 @@ SYNOPSIS
|
|||
| --remove-restricted-services=[RESTRICTED-SERVICES,...]]
|
||||
[--clear-egress-policies | --set-egress-policies=YAML_FILE]
|
||||
[--clear-ingress-policies | --set-ingress-policies=YAML_FILE]
|
||||
[--enable-vpc-accessible-services
|
||||
--add-vpc-allowed-services=[VPC-ALLOWED-SERVICES,...]
|
||||
[--clear-vpc-accessible-services
|
||||
| --set-vpc-accessible-services=YAML_FILE
|
||||
| --enable-vpc-accessible-services
|
||||
--add-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
| --clear-vpc-allowed-services
|
||||
| --remove-vpc-allowed-services=[VPC-ALLOWED-SERVICES,...]]
|
||||
| --remove-vpc-allowed-services=[VPC_SERVICE,...]]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -156,26 +158,44 @@ FLAGS
|
|||
For more information about non-alpha versions, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1/accessPolicies.servicePerimeters
|
||||
|
||||
Arguments for configuring VPC accessible service restrictions.
|
||||
These flags modify the VpcAccessibleServices of this ServicePerimeter
|
||||
config.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-vpc-accessible-services
|
||||
Empties existing enforced VpcAccessibleServices.
|
||||
|
||||
--set-vpc-accessible-services=YAML_FILE
|
||||
Path to a file containing a VpcAccessibleServices object.
|
||||
|
||||
This file contains a YAML-compliant object representing
|
||||
VpcAccessibleServices described in the API reference.
|
||||
|
||||
For more information about the alpha version, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1alpha/accessPolicies.servicePerimeters
|
||||
For more information about non-alpha versions, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1/accessPolicies.servicePerimeters
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
When specified restrict API calls within the Service Perimeter to the
|
||||
set of vpc allowed services. To disable use
|
||||
'--no-enable-vpc-accessible-services'.
|
||||
|
||||
These flags modify the member VPC Allowed Services of this Service
|
||||
Perimeter.
|
||||
These flags modify the member vpc allowed services of this perimeter.
|
||||
Services allowed to be called within the Perimeter when VPC Accessible
|
||||
Services is enabled
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--add-vpc-allowed-services=[VPC-ALLOWED-SERVICES,...]
|
||||
Append the given values to the current VPC Allowed Services.
|
||||
--add-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Append the given values to the current vpc allowed services.
|
||||
|
||||
--clear-vpc-allowed-services
|
||||
Empty the current VPC Allowed Services.
|
||||
Empty the current vpc allowed services.
|
||||
|
||||
--remove-vpc-allowed-services=[VPC-ALLOWED-SERVICES,...]
|
||||
Remove the given values from the current VPC Allowed Services.
|
||||
--remove-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Remove the given values from the current vpc allowed services.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
|
|
@ -17,7 +17,9 @@ SYNOPSIS
|
|||
| --set-restricted-services=[SERVICE,...]]
|
||||
[--clear-egress-policies | --set-egress-policies=YAML_FILE]
|
||||
[--clear-ingress-policies | --set-ingress-policies=YAML_FILE]
|
||||
[--enable-vpc-accessible-services
|
||||
[--clear-vpc-accessible-services
|
||||
| --set-vpc-accessible-services=YAML_FILE
|
||||
| --enable-vpc-accessible-services
|
||||
--add-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
| --clear-vpc-allowed-services
|
||||
| --remove-vpc-allowed-services=[VPC_SERVICE,...]]
|
||||
|
|
@ -181,25 +183,44 @@ FLAGS
|
|||
For more information about non-alpha versions, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1/accessPolicies.servicePerimeters
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
When specified restrict API calls within the Service Perimeter to the
|
||||
set of vpc allowed services. To disable use
|
||||
'--no-enable-vpc-accessible-services'.
|
||||
|
||||
These flags modify the member vpc allowed services of this perimeter.
|
||||
Services allowed to be called within the Perimeter when VPC Accessible
|
||||
Services is enabled
|
||||
These flags modify the VpcAccessibleServices of this ServicePerimeter
|
||||
config.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--add-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Append the given values to the current vpc allowed services.
|
||||
--clear-vpc-accessible-services
|
||||
Empties existing enforced VpcAccessibleServices.
|
||||
|
||||
--clear-vpc-allowed-services
|
||||
Empty the current vpc allowed services.
|
||||
--set-vpc-accessible-services=YAML_FILE
|
||||
Path to a file containing a VpcAccessibleServices object.
|
||||
|
||||
--remove-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Remove the given values from the current vpc allowed services.
|
||||
This file contains a YAML-compliant object representing
|
||||
VpcAccessibleServices described in the API reference.
|
||||
|
||||
For more information about the alpha version, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1alpha/accessPolicies.servicePerimeters
|
||||
For more information about non-alpha versions, see:
|
||||
https://cloud.google.com/access-context-manager/docs/reference/rest/v1/accessPolicies.servicePerimeters
|
||||
|
||||
--enable-vpc-accessible-services
|
||||
When specified restrict API calls within the Service Perimeter to the
|
||||
set of vpc allowed services. To disable use
|
||||
'--no-enable-vpc-accessible-services'.
|
||||
|
||||
These flags modify the member vpc allowed services of this perimeter.
|
||||
Services allowed to be called within the Perimeter when VPC Accessible
|
||||
Services is enabled
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--add-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Append the given values to the current vpc allowed services.
|
||||
|
||||
--clear-vpc-allowed-services
|
||||
Empty the current vpc allowed services.
|
||||
|
||||
--remove-vpc-allowed-services=[VPC_SERVICE,...]
|
||||
Remove the given values from the current vpc allowed services.
|
||||
|
||||
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