gcloud scc manage custom-modules sha list-descendant Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud scc manage custom-modules sha list-descendant - list the details of the resident and descendant Security Health Analytics custom modules
- SYNOPSIS
gcloud scc manage custom-modules sha list-descendant(--folder=FOLDER_ID|--organization=ORGANIZATION_ID|--parent=PARENT|--project=PROJECT_ID_OR_NUMBER)[--filter=EXPRESSION][--limit=LIMIT][--page-size=PAGE_SIZE][--sort-by=[FIELD,…]][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
- List the details of the resident and descendant Security Health Analytics custommodules for a specified organization or folder. For a project, this commandlists only the custom modules that are created in the project. Modules createdin a parent organization or folder are excluded from the list. To list theresident custom modules and the modules that are inherited from a parentorganization and folder, use gcloud scc manage custom-modules sha list.
- EXAMPLES
- To list resident and inherited Security Health Analytics custom modules fororganization
123, run:gcloudsccmanagecustom-modulesshalist-descendant--organization=organizations/123To list resident and inherited Security Health Analytics custom modules forfolder
456, run:gcloudsccmanagecustom-modulesshalist-descendant--folder=folders/456To list resident and inherited Security Health Analytics custom modules forproject
789, run:gcloudsccmanagecustom-modulesshalist-descendant--project=projects/789 - REQUIRED FLAGS
- Exactly one of these must be specified:
--folder=FOLDER_ID- Folder associated with the custom module.
--organization=ORGANIZATION_ID- Organization associated with the custom module.
--parent=PARENT- Parent associated with the custom module. Can be one oforganizations/<id>, projects/<id or name>, folders/<id>
--project=PROJECT_ID_OR_NUMBER- Project associated with the custom module.
- 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. - NOTES
- This variant is also available:
gcloudalphasccmanagecustom-modulesshalist-descendant
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.