mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 23:08:48 +00:00
gcloud: Wed Apr 12 10:43:12 UTC 2023
This commit is contained in:
parent
32e56b8b99
commit
b155beb241
220 changed files with 7834 additions and 1142 deletions
|
|
@ -1,6 +1,6 @@
|
|||
NAME
|
||||
gcloud alpha scc custom-modules sha get - get a Security Health Analytics
|
||||
custom module
|
||||
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
|
||||
|
|
@ -8,56 +8,52 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Get a Security Health Analytics custom module.
|
||||
(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 a Security Health Analytics custom module with id 123456 for
|
||||
organization 123, run:
|
||||
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
|
||||
$ gcloud alpha scc custom-modules sha get 123456 --organization=123
|
||||
$ gcloud alpha scc custom-modules sha get \
|
||||
organizations/123/securityHealthAnalyticsSettings/\
|
||||
customModules/123456
|
||||
|
||||
To get a Security Health Analytics custom module with id 123456 for folder
|
||||
456, run:
|
||||
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
|
||||
$ gcloud alpha scc custom-modules sha get 123456 --folder=456
|
||||
$ gcloud alpha scc custom-modules sha get \
|
||||
folders/456/securityHealthAnalyticsSettings/customModules/123456
|
||||
|
||||
To get a Security Health Analytics custom module with id 123456 for project
|
||||
789, run:
|
||||
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
|
||||
$ gcloud alpha scc custom-modules sha get 123456 --project=789
|
||||
$ gcloud alpha scc custom-modules sha get \
|
||||
projects/789/securityHealthAnalyticsSettings/customModules/\
|
||||
123456
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
CUSTOM_MODULE
|
||||
Id or the full resource name of the Security Health Analytics 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 where the Security Health Analytics custom module resides.
|
||||
Formatted as folders/456 or just 456.
|
||||
Folder from which to get the custom module details. Formatted as
|
||||
folders/456 or just 456.
|
||||
|
||||
--organization=ORGANIZATION
|
||||
Organization where the Security Health Analytics custom module
|
||||
resides. Formatted as organizations/123 or just 123.
|
||||
Organization from which to get the custom module details. Formatted
|
||||
as organizations/123 or just 123.
|
||||
|
||||
--project=PROJECT
|
||||
Project (id or number) where the Security Health Analytics custom
|
||||
module resides. Formatted as projects/789 or just 789.
|
||||
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,
|
||||
|
|
@ -75,5 +71,7 @@ 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.
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud scc custom-modules sha get
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue