gcloud beta essential-contacts compute

NAME: gcloud beta essential-contacts compute - compute the essential contacts that are subscribed to the specified notification categories for a resource
SYNOPSIS: gcloud beta essential-contacts compute --notification-categories=[NOTIFICATION_CATEGORIES,…] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,…]] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: (BETA) This command will return the contacts subscribed to any of the notification categories that have been set on the requested resource or any of its ancestors.
EXAMPLES: To compute contacts subscribed to the technical category for the current project, run:
gcloud beta essential-contacts compute --notification-categories=technical

To compute contacts subscribed to the product-updates or billing categories for the folder with id 123, run:
gcloud beta essential-contacts compute --notification-categories=product-updates,billing --folder=123

To compute contacts subscribed to the legal category for the organization with id 456, run:
gcloud beta essential-contacts compute --notification-categories=legal --organization=456
REQUIRED FLAGS: --notification-categories=[NOTIFICATION_CATEGORIES,…]

list of notification categories contact is subscribed to. NOTIFICATION_CATEGORIES must be one of: all, billing, legal, notification-category-unspecified, product-updates, security, suspension, technical, technical-incidents.
FLAGS: 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.
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

Some services group resource list output into pages. This flag specifies the maximum number of resources per page. The default is determined by the service if it supports paging, otherwise it is unlimited (no paging). 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. These variants are also available:
gcloud essential-contacts compute

gcloud alpha essential-contacts compute