mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-10 19:31:55 +00:00
77 lines
2.9 KiB
Text
77 lines
2.9 KiB
Text
NAME
|
|
gcloud alpha scc custom-modules sha get - get the details of a Security
|
|
Health Analytics custom module
|
|
|
|
SYNOPSIS
|
|
gcloud alpha scc custom-modules sha get CUSTOM_MODULE
|
|
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
|
|
[GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) Get the details of a Security Health Analytics custom module. It
|
|
does not resolve INHERITED enablement states to ENABLED or DISABLED for
|
|
modules created at ancestor levels. For example, if the module is enabled
|
|
at the ancestor level, modules for all child resources will have the
|
|
enablement state set to INHERITED. Use gcloud scc custom-modules sha
|
|
get-effective to retrieve a custom module with its effective enablement
|
|
state.
|
|
|
|
EXAMPLES
|
|
To get the details of a Security Health Analytics custom module with ID
|
|
123456 for organization 123, run:
|
|
|
|
$ gcloud alpha scc custom-modules sha get 123456 \
|
|
--organization=organizations/123
|
|
|
|
To get the details of a Security Health Analytics custom module with ID
|
|
123456 for folder 456, run:
|
|
|
|
$ gcloud alpha scc custom-modules sha get 123456 --folder=folders/456
|
|
|
|
To get the details of a Security Health Analytics custom module with ID
|
|
123456 for project 789, run:
|
|
|
|
$ gcloud alpha scc custom-modules sha get 123456 \
|
|
--project=projects/789
|
|
|
|
POSITIONAL ARGUMENTS
|
|
CUSTOM_MODULE
|
|
ID or the full resource name of the Security Health Analytics custom
|
|
module. If you specify the full resource name, you do not need to
|
|
specify the --organization, --folder, or --project flags.
|
|
|
|
FLAGS
|
|
At most one of these can be specified:
|
|
|
|
--folder=FOLDER
|
|
Folder from which to get the custom module details. Formatted as
|
|
folders/456 or just 456.
|
|
|
|
--organization=ORGANIZATION
|
|
Organization from which to get the custom module details. Formatted
|
|
as organizations/123 or just 123.
|
|
|
|
--project=PROJECT
|
|
ID or number of the project from which to get the custom module
|
|
details. Formatted as projects/789 or just 789.
|
|
|
|
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.
|
|
|
|
API REFERENCE
|
|
This command uses the securitycenter/v1 API. The full documentation for
|
|
this API can be found at: https://cloud.google.com/security-command-center
|
|
|
|
NOTES
|
|
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 scc custom-modules sha get
|
|
|