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

gcloud: Tue Nov 18 10:53:36 UTC 2025

Browse source
This commit is contained in:
Automated 2025-11-18 10:53:36 +00:00
parent 4b21ae6795
commit e1ec13485a
380 changed files with 16045 additions and 783 deletions
Download patch file Download diff file Expand all files Collapse all files

78
gcloud/beta/services/disable
View file

@ -1,10 +1,13 @@
NAME
gcloud beta services disable - disable a service for consumption for a
project
project, folder or organization
SYNOPSIS
gcloud beta services disable [SERVICE ...] [--async] [--force]
[GCLOUD_WIDE_FLAG ...]
gcloud beta services disable [SERVICE ...] [--async]
[--bypass-api-usage-check] [--force] [--validate-only]
[--bypass-dependency-service-check | --disable-dependency-services]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command disables one or more previously-enabled services for
@ -19,11 +22,28 @@ DESCRIPTION
a service at: https://cloud.google.com/service-usage/docs/enable-disable
EXAMPLES
To disable a service called my-consumed-service for the active project,
To disable a service called my-consumed-service for the current project,
run:
$ gcloud beta services disable my-consumed-service
To disable a service called my-consumed-service for the project my-project,
run:
$ gcloud beta services disable my-consumed-service \
--project=my-project
To disable a service called my-consumed-service for the folder my-folder,
run:
$ gcloud beta services disable my-consumed-service --folder=my-folder
To disable a service called my-consumed-service for the organization
my-organization, run:
$ gcloud beta services disable my-consumed-service \
--organization=my-organization
To run the same command asynchronously (non-blocking), run:
$ gcloud beta services disable my-consumed-service --async
@ -37,12 +57,54 @@ FLAGS
Return immediately, without waiting for the operation in progress to
complete.
--bypass-api-usage-check
If specified, the system will bypass usage checks for services that are
being removed. Otherwise, the system will check if the service to be
removed was used in the last 30 days or enabled in the last 3 days. If
so, the system will return an error.
--force
If specified, the disable call will proceed even if there are enabled
services which depend on the service to be disabled or disable the
service used in last 30 days or was enabled in recent 3 days. Forcing
the call means that the services which depend on the service to be
disabled will also be disabled.
services which depend on the service to be disabled, or the service to
be disabled was used in the last 30 days, or the service to be disabled
was enabled in the last 3 days. Forcing the call means that the
services which depend on the service to be disabled will also be
disabled. (Note): If --bypass-api-usage-check,
--bypass-dependency-service-check, or --disable-dependency-services
flags are used, they will take precedence over --force.
--validate-only
Validate the disable action, but don't actually perform it
At most one of these can be specified:
--bypass-dependency-service-check
If specified, the disable call will bypass the check for dependencies
and the dependencies will remain enabled.
--disable-dependency-services
If specified, the disable call will proceed disabling the service and
all the enabled services depend on the service to be disabled
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

54
gcloud/beta/services/enable
View file

@ -1,12 +1,16 @@
NAME
gcloud beta services enable - enables a service for consumption for a
project
project, folder or organization
SYNOPSIS
gcloud beta services enable [SERVICE ...] [--async] [GCLOUD_WIDE_FLAG ...]
gcloud beta services enable [SERVICE ...] [--async] [--skip-dependency]
[--validate-only]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command enables a service for consumption for a project.
(BETA) This command enables a service for consumption for a project, folder
or organization.
To see a list of available services for a project, run:
@ -21,6 +25,23 @@ EXAMPLES
$ gcloud beta services enable my-consumed-service
To enable a service called my-consumed-service on the project my-project,
run:
$ gcloud beta services enable my-consumed-service \
--project=my-project
To enable a service called my-consumed-service on the folder my-folder,
run:
$ gcloud beta services enable my-consumed-service --folder=my-folder
To enable a service called my-consumed-service on the organization
my-organization, run:
$ gcloud beta services enable my-consumed-service \
--organization=my-organization
To run the same command asynchronously (non-blocking), run:
$ gcloud beta services enable my-consumed-service --async
@ -39,6 +60,33 @@ FLAGS
Return immediately, without waiting for the operation in progress to
complete.
--skip-dependency
If set, the dependencies of the service to be enabled will not be
enabled.
--validate-only
Validate the enable action, but don't actually perform it
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

9
gcloud/beta/services/groups/help
View file

@ -12,6 +12,15 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
list-expanded-members
(BETA) List expanded members of a specific service and group.
list-members
(BETA) List members of a specific service and group.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:

93
gcloud/beta/services/groups/list-expanded-members Normal file
View file

@ -0,0 +1,93 @@
NAME
gcloud beta services groups list-expanded-members - list expanded members
of a specific service and group
SYNOPSIS
gcloud beta services groups list-expanded-members SERVICE GROUP
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE; default=50] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List expanded members of a specific service and group.
EXAMPLES
List expanded members of service my-service and group my-group:
$ gcloud beta services groups list-expanded-members my-service \
my-group
List expanded members of service my-service and group my-group for a
specific project '12345678':
$ gcloud beta services groups list-expanded-members my-service \
my-group --project=12345678
POSITIONAL ARGUMENTS
SERVICE
Name of the service.
GROUP
Service group name, for example "dependencies".
FLAGS
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE; default=50
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is 50.
Paging may be applied before or after --filter and --limit depending on
the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
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 services groups list-expanded-members

92
gcloud/beta/services/groups/list-members Normal file
View file

@ -0,0 +1,92 @@
NAME
gcloud beta services groups list-members - list members of a specific
service and group
SYNOPSIS
gcloud beta services groups list-members SERVICE GROUP
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE; default=50] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List members of a specific service and group.
EXAMPLES
List members of service my-service and group my-group:
$ gcloud beta services groups list-members my-service my-group
List members of service my-service and group my-group for a specific
project '12345678':
$ gcloud beta services groups list-members my-service my-group \
--project=12345678
POSITIONAL ARGUMENTS
SERVICE
Name of the service.
GROUP
Service group name, for example "dependencies".
FLAGS
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE; default=50
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is 50.
Paging may be applied before or after --filter and --limit depending on
the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
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 services groups list-members

11
gcloud/beta/services/help
View file

@ -38,6 +38,9 @@ GROUPS
identity
(BETA) Manage service identity.
mcp
(BETA) List, enable and disable MCP endpoints.
operations
(BETA) Manage Operation for various services.
@ -54,13 +57,15 @@ COMMANDS
COMMAND is one of the following:
disable
(BETA) Disable a service for consumption for a project.
(BETA) Disable a service for consumption for a project, folder or
organization.
enable
(BETA) Enables a service for consumption for a project.
(BETA) Enables a service for consumption for a project, folder or
organization.
list
(BETA) List services for a project.
(BETA) List services for a project, folder or organization.
NOTES
This command is currently in beta and might change without notice. These

70
gcloud/beta/services/list
View file

@ -1,47 +1,61 @@
NAME
gcloud beta services list - list services for a project
gcloud beta services list - list services for a project, folder or
organization
SYNOPSIS
gcloud beta services list [--available | --enabled] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE; default=200]
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
gcloud beta services list [--available | --enabled]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command lists the services that are enabled or available to be
enabled by a project. You can choose the mode in which the command will
list services by using exactly one of the --enabled or --available flags.
--enabled is the default.
enabled by a project, folder or organization. Service enablement and
availability can be inherited from resource ancestors. A resource's enabled
services include services that are enabled on the resource itself and
enabled on all resource ancestors. services by using exactly one of the
--enabled or --available flags. --enabled is the default.
EXAMPLES
To list the services for the current project has enabled for consumption,
run:
To list the services the current project has enabled for consumption, run:
$ gcloud beta services list --enabled
To list the services for the current project can enable for consumption,
run:
To list the services the current project can enable for consumption, run:
$ gcloud beta services list --available
To list the services for project my-project has enabled for consumption,
run:
$ gcloud beta services list --enabled --project=my-project
To list the services the project my-project can enable for consumption,
run:
$ gcloud beta services list --available --project=my-project
FLAGS
At most one of these can be specified:
--available
Return the services available to the project to enable. This list
will include any services that the project has already enabled.
Return the services available to the project, folder or organization
to enable.
--enabled
(DEFAULT) Return the services which the project has enabled.
(DEFAULT) Return the services which the project, folder or
organization has enabled.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
LIST COMMAND FLAGS
--filter=EXPRESSION
@ -56,11 +70,11 @@ LIST COMMAND FLAGS
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE; default=200
--page-size=PAGE_SIZE; default=1000
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is 200.
Paging may be applied before or after --filter and --limit depending on
the service.
specifies the maximum number of resources per page. The default is
1000. Paging may be applied before or after --filter and --limit
depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The

40
gcloud/beta/services/mcp/content-security/add Normal file
View file

@ -0,0 +1,40 @@
NAME
gcloud beta services mcp content-security add - add MCP content security
provider of a project
SYNOPSIS
gcloud beta services mcp content-security add MCP_CONTENT_SECURITY_PROVIDER
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Add MCP content security provider of a project.
EXAMPLES
Add MCP content security provider of a project:
$ gcloud beta services mcp content-security add \
my-mcp-content-security-provider
Add MCP content security provider of a project my-project:
$ gcloud beta services mcp content-security add \
my-mcp-content-security-provider --project=my-project
POSITIONAL ARGUMENTS
MCP_CONTENT_SECURITY_PROVIDER
The MCP content security provider to add.
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 services mcp content-security add

33
gcloud/beta/services/mcp/content-security/get Normal file
View file

@ -0,0 +1,33 @@
NAME
gcloud beta services mcp content-security get - get MCP content security
providers for a project
SYNOPSIS
gcloud beta services mcp content-security get [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get MCP content security providers for a project.
EXAMPLES
Get MCP content security providers for a project:
$ gcloud beta services mcp content-security get
Get MCP content security providers for a project my-project:
$ gcloud beta services mcp content-security get --project=my-project
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 services mcp content-security get

33
gcloud/beta/services/mcp/content-security/help Normal file
View file

@ -0,0 +1,33 @@
NAME
gcloud beta services mcp content-security - get/add/remove MCP content
security
SYNOPSIS
gcloud beta services mcp content-security COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get/add/remove MCP content security.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
add
(BETA) Add MCP content security provider of a project.
get
(BETA) Get MCP content security providers for a project.
remove
(BETA) Remove MCP content security provider of a project.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha services mcp content-security

40
gcloud/beta/services/mcp/content-security/remove Normal file
View file

@ -0,0 +1,40 @@
NAME
gcloud beta services mcp content-security remove - remove MCP content
security provider of a project
SYNOPSIS
gcloud beta services mcp content-security remove
MCP_CONTENT_SECURITY_PROVIDER [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Remove MCP content security provider of a project.
EXAMPLES
Remove MCP content security provider of a project:
$ gcloud beta services mcp content-security remove \
my-mcp-content-security-provider
Remove MCP content security provider of a project my-project:
$ gcloud beta services mcp content-security remove \
my-mcp-content-security-provider --project=my-project
POSITIONAL ARGUMENTS
MCP_CONTENT_SECURITY_PROVIDER
The MCP content security provider to remove.
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 services mcp content-security remove

80
gcloud/beta/services/mcp/disable Normal file
View file

@ -0,0 +1,80 @@
NAME
gcloud beta services mcp disable - disable a service for MCP on a project,
folder or organization
SYNOPSIS
gcloud beta services mcp disable SERVICE [--async]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Disable a service for MCP on a project, folder or organization
EXAMPLES
To disable a service for MCP called my-service on the current project, run:
$ gcloud beta services mcp disable my-service
To disable a service for MCP called my-service on the project my-project,
run:
$ gcloud beta services mcp disable my-service --project=my-project
To disable a service for MCP called my-service on the folder my-folder,
run:
$ gcloud beta services mcp disable my-service --folder=my-folder
To disable a service for MCP called my-service on the organization
my-organization, run:
$ gcloud beta services mcp disable my-service \
--organization=my-organization
To run the same command asynchronously (non-blocking), run:
$ gcloud beta services mcp disable my-service --async
POSITIONAL ARGUMENTS
SERVICE
The name of the service to disable MCP.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
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 services mcp disable

84
gcloud/beta/services/mcp/enable Normal file
View file

@ -0,0 +1,84 @@
NAME
gcloud beta services mcp enable - enable a service for MCP on a project,
folder or organization
SYNOPSIS
gcloud beta services mcp enable SERVICE [--async]
[--skip-mcp-endpoint-check]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Enable a service for MCP on a project, folder or organization
EXAMPLES
To enable a service for MCP called my-service on the current project, run:
$ gcloud beta services mcp enable my-service
To enable a service for MCP called my-service on the project my-project,
run:
$ gcloud beta services mcp enable my-service --project=my-project
To enable a service for MCP called my-service on the folder my-folder, run:
$ gcloud beta services mcp enable my-service --folder=my-folder
To enable a service for MCP called my-service on the organization
my-organization, run:
$ gcloud beta services mcp enable my-service \
--organization=my-organization
To run the same command asynchronously (non-blocking), run:
$ gcloud beta services mcp enable my-service --async
POSITIONAL ARGUMENTS
SERVICE
The name of the service to enable MCP.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--skip-mcp-endpoint-check
If true, the system will bypass the check for MCP endpoint while
enabling a service.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
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 services mcp enable

38
gcloud/beta/services/mcp/help Normal file
View file

@ -0,0 +1,38 @@
NAME
gcloud beta services mcp - list, enable and disable MCP endpoints
SYNOPSIS
gcloud beta services mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List, enable and disable MCP endpoints.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
content-security
(BETA) Get/add/remove MCP content security.
COMMANDS
COMMAND is one of the following:
disable
(BETA) Disable a service for MCP on a project, folder or organization.
enable
(BETA) Enable a service for MCP on a project, folder or organization.
list
(BETA) List MCP services for a project, folder or organization.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha services mcp

95
gcloud/beta/services/mcp/list Normal file
View file

@ -0,0 +1,95 @@
NAME
gcloud beta services mcp list - list MCP services for a project, folder or
organization
SYNOPSIS
gcloud beta services mcp list [--available | --enabled]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command lists the MCP services that are enabled or available
(with MCP endpoints) to be MCP enabled by a project, folder or
organization.
EXAMPLES
To list the services the current project has enabled for MCP, run:
$ gcloud beta services mcp list --enabled
To list the services the current project can enable for MCP, run:
$ gcloud beta services mcp list --available
FLAGS
At most one of these can be specified:
--available
Return the services available to the project, folder or organization
to enable for MCP.
--enabled
(DEFAULT) Return the MCP services which the project, folder or
organization has enabled.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE; default=1000
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
1000. Paging may be applied before or after --filter and --limit
depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
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 services mcp list

68
gcloud/beta/services/policies/get Normal file
View file

@ -0,0 +1,68 @@
NAME
gcloud beta services policies get - get consumer policy for a project,
folder or organization
SYNOPSIS
gcloud beta services policies get [--output-file=OUTPUT_FILE]
[--policy-name=POLICY_NAME; default="default"]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get consumer policy for a project, folder or organization.
EXAMPLES
Get consumer policy for default policy on current project:
$ gcloud beta services policies get OR $ gcloud beta services \
policies get --policy-name=default
Get consumer policy for default policy on current project and save the
content in an output file:
$ gcloud beta services policies get \
--output-file=/path/to/the/file.yaml OR $ gcloud beta services \
policies get --output-file=/path/to/the/file.json
FLAGS
--output-file=OUTPUT_FILE
Path to the file to write policy contents to. Supported format:.yaml or
.json.
--policy-name=POLICY_NAME; default="default"
Name of the consumer policy. Currently only "default" is supported.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
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 services policies get

61
gcloud/beta/services/policies/get-effective Normal file
View file

@ -0,0 +1,61 @@
NAME
gcloud beta services policies get-effective - get effective policy for a
project, folder or organization
SYNOPSIS
gcloud beta services policies get-effective [--view=VIEW; default="BASIC"]
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get effective policy for a project, folder or organization.
EXAMPLES
Get effective policy for the current project:
$ gcloud beta services policies get-effective
Get effective policy for project my-project:
$ gcloud beta services policies get-effective --project=my-project
FLAGS
--view=VIEW; default="BASIC"
The view of the effective policy. BASIC includes basic metadata about
the effective policy. FULL includes every information related to
effective policy. VIEW must be one of: BASIC, FULL.
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
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 services policies get-effective

16
gcloud/beta/services/policies/help
View file

@ -13,6 +13,22 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
get
(BETA) Get consumer policy for a project, folder or organization.
get-effective
(BETA) Get effective policy for a project, folder or organization.
test-enabled
(BETA) Test a value against the result of merging consumer policies in
the resource hierarchy.
update
(BETA) Update consumer policy for a project, folder or organization.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:

62
gcloud/beta/services/policies/test-enabled Normal file
View file

@ -0,0 +1,62 @@
NAME
gcloud beta services policies test-enabled - test a value against the
result of merging consumer policies in the resource hierarchy
SYNOPSIS
gcloud beta services policies test-enabled SERVICE
[--folder=FOLDER_ID | --organization=ORGANIZATION_ID
| --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Test a value against the result of merging consumer policies in the
resource hierarchy.
EXAMPLES
Test for service my-service for current project:
$ gcloud beta services policies test-enabled my-service
Test for service my-service for project my-project:
$ gcloud beta services policies test-enabled my-service \
--project=my-project
POSITIONAL ARGUMENTS
SERVICE
Name of the service.
FLAGS
At most one of these can be specified:
--folder=FOLDER_ID
The Google Cloud Platform folder ID to use for this invocation.
--organization=ORGANIZATION_ID
The Google Cloud Platform organization ID to use for this invocation.
--project=PROJECT_ID
The Google Cloud project ID to use for this invocation. If omitted,
then the current project is assumed; the current project can be
listed using gcloud config list --format='text(core.project)' and can
be set using gcloud config set project PROJECTID.
--project and its fallback core/project property play two roles in
the invocation. It specifies the project of the resource to operate
on. It also specifies the project for API enablement check, quota,
and billing. To specify a different project for quota and billing,
use --billing-project or billing/quota_project property.
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 services policies test-enabled

72
gcloud/beta/services/policies/update Normal file
View file

@ -0,0 +1,72 @@
NAME
gcloud beta services policies update - update consumer policy for a
project, folder or organization
SYNOPSIS
gcloud beta services policies update
--consumer-policy-file=CONSUMER_POLICY_FILE [--bypass-api-usage-check]
[--bypass-dependency-check] [--validate-only] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update consumer policy for a project, folder or organization.
EXAMPLES
Update consumer policy
$ gcloud beta services policies update \
--consumer-policy-file=/path/to/the/file.yaml
Validate the update action on the policy:
$ gcloud beta services policies update \
--consumer-policy-file=/path/to/the/file.yaml --validate-only
Update consumer policy and bypass dependency check:
$ gcloud beta services policies update \
--consumer-policy-file=/path/to/the/file.yaml \
--bypass-dependency-check
Update consumer policy and bypass api usage check:
$ gcloud beta services policies update \
--consumer-policy-file=/path/to/the/file.yaml \
--bypass-api-usage-check
REQUIRED FLAGS
--consumer-policy-file=CONSUMER_POLICY_FILE
Path to the file that contains the consumer policy in the YAML format.
OPTIONAL FLAGS
--bypass-api-usage-check
If true, the system will bypass usage checks for services that are
being removed. If false, the system will check if the service to be
removed was used in the last 30 days or enabled in the last 3 days. If
so, an error will be returned.
--bypass-dependency-check
This flag controls dependency management within the consumer policy. If
false, dependencies are enforced. When adding a new service, it
verifies that all the services dependencies are already present in the
policy. When removing a service, the system will ensure that no other
services in the policy depend on it. If the policy lacks any required
dependencies, the update will not succeed, and an error will be
returned.
--validate-only
Validate the to update action, but don't actually perform it
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 services policies update