gcloud alpha essential-contacts delete - delete an essential contact
gcloud alpha essential-contacts delete CONTACT_ID [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...]
To delete the contact with id 123 in the current project, run:
$ gcloud alpha essential-contacts delete 123
To delete the contact with id 123 in the folder with id 456, run:
$ gcloud alpha essential-contacts delete 123 --folder=456
To delete the contact with id 123 in the organization with id 456, run:
$ gcloud alpha essential-contacts delete 123 --organization=456
- CONTACT_ID
id of contact to delete.
- At most one of these can be specified:
- --folder=FOLDER
folder number where contacts are set. If neither --project, --folder, nor --organization are provided then the config property [core/project] will be used as the resource.
- --organization=ORGANIZATION
organization number where contacts are set. If neither --project, --folder, nor --organization are provided then the config property [core/project] will be used as the resource.
- --project=PROJECT
project number or id where contacts are set. If neither --project, --folder, nor --organization are provided then the config property [core/project] will be used as the resource.
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. These variants are also available:
$ gcloud essential-contacts delete
$ gcloud beta essential-contacts delete