gcloud alpha services disable

gcloud alpha services disable - disable a service for consumption for a project, folder or organization

gcloud alpha services disable SERVICE [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 …]

To see a list of the enabled services for a project, run:

gcloudalphaserviceslist 

More information on listing services can be found at: https://cloud.google.com/service-usage/docs/list-services and on disabling a service at: https://cloud.google.com/service-usage/docs/enable-disable

gcloudalphaservicesdisablemy-consumed-service

To disable a service called my-consumed-service for the project my-project, run:

gcloudalphaservicesdisablemy-consumed-service--project=my-project

To disable a service called my-consumed-service for the folder my-folder, run:

gcloudalphaservicesdisablemy-consumed-service--folder=my-folder

To disable a service called my-consumed-service for the organization my-organization, run:

gcloudalphaservicesdisablemy-consumed-service--organization=my-organization

To run the same command asynchronously (non-blocking), run:

gcloudalphaservicesdisablemy-consumed-service--async

SERVICE [SERVICE …]

The name of the service(s) to disable.

--async

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 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.

Run $ gcloud help for details.