gcloud alpha dataplex lakes deauthorize - deauthorize a project service account from managing given resource
gcloud alpha dataplex lakes deauthorize (--project-resource=PROJECT_RESOURCE | --storage-bucket-resource=STORAGE_BUCKET_RESOURCE | --bigquery-dataset-resource=BIGQUERY_DATASET_RESOURCE --secondary-project=SECONDARY_PROJECT) [GCLOUD_WIDE_FLAG ...]
(ALPHA) Remove IAM Bindings for the service account of the primary project from a secondary project, a storage bucket, or BigQuery dataset.
To deauthorize the service account in project test-project from managing another project test-project2, run:
$ gcloud alpha dataplex lakes deauthorize --project=test-project \ --project-resource=test-project2
To deauthorize the service account in project test-project from managing the storage bucket dataplex-storage-bucket, run:
$ gcloud alpha dataplex lakes deauthorize --project=test-project \ --storage-bucket-resource=dataplex-storage-bucket
To deauthorize the service account in project test-project from managing the BigQuery dataset test-dataset in project test-project2, run:
$ gcloud alpha dataplex lakes deauthorize --project=test-project \ --bigquery-dataset-resource=test-dataset \ --secondary-project=test-project2
- Container or Object to unbind p4sa
Exactly one of these must be specified:
- --project-resource=PROJECT_RESOURCE
The identifier of the project to deauthorize.
- --storage-bucket-resource=STORAGE_BUCKET_RESOURCE
The identifier of the Cloud Storage bucket to deauthorize the project from.
- Fields to help identify the BigQuery Dataset.
- --bigquery-dataset-resource=BIGQUERY_DATASET_RESOURCE
The identifier of the BigQuery dataset to deauthorize the project from.
This flag argument must be specified if any of the other arguments in this group are specified.
- --secondary-project=SECONDARY_PROJECT
The identifier of the Project where BigQuery dataset resides
This flag argument must be specified if any of the other arguments in this group are specified.
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.
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available:
$ gcloud dataplex lakes deauthorize