gcloud scc custom-modules sha list Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud scc custom-modules sha list - list the details of Security Health Analytics custom modules
- SYNOPSIS
gcloud scc custom-modules sha list(--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT)[--filter=EXPRESSION][--limit=LIMIT][--page-size=PAGE_SIZE][--sort-by=[FIELD,…]][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
- List the details of the resident and inherited Security Health Analytics custommodules for the specified folder or project. For an organization, this commandlists only the custom modules that are created at the organization level. Custommodules created in child folders or projects are not included in the list. Tolist the resident custom modules and the modules that are created in childfolders or projects, use
gcloud scccustom-modules sha list-descendant. - EXAMPLES
- To list resident and inherited Security Health Analytics custom modules fororganization
123, run:gcloudscccustom-modulesshalist--organization=organizations/123To list resident and inherited Security Health Analytics custom modules forfolder
456, run:gcloudscccustom-modulesshalist--folder=folders/456To list resident and inherited Security Health Analytics custom modules forproject
789, run:gcloudscccustom-modulesshalist--project=projects/789 - REQUIRED FLAGS
- Exactly one of these must be specified:
--folder=FOLDER- Folder for listing the Security Health Analytics custom modules created at thecurrent folder level and inherited modules from CRM ancestors. Formatted as
folders/456or just456. --organization=ORGANIZATION- Organization for listing the Security Health Analytics custom modules created atthe organization level. Formatted as
organizations/123or just123. --project=PROJECT- ID or number of the project for listing the Security Health Analytics custommodules created at current project level and inherited modules from CRMancestors. Formatted as
projects/789or just789.
- Exactly one of these must be specified:
- LIST COMMAND FLAGS
--filter=EXPRESSION- Apply a Boolean filter
EXPRESSIONto each resource itemto be listed. If the expression evaluatesTrue, then that item islisted. For more details and examples of filter expressions, run $gcloud topic filters. This flaginteracts 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. Thisflag 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 themaximum number of resources per page. The default is determined by the serviceif it supports paging, otherwise it is
unlimited(no paging).Paging may be applied before or after--filterand--limitdepending on the service. --sort-by=[FIELD,…]- Comma-separated list of resource field key names to sort by. The default orderis ascending. Prefix a field with ``~´´ for descending order on thatfield. 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 helpfor details. - API REFERENCE
- This command uses the
securitycenter/v1API. The full documentationfor this API can be found at:https://cloud.google.com/security-command-center - NOTES
- This variant is also available:
gcloudalphascccustom-modulesshalist
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.