imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 02:25:19 +00:00
Code Activity

gcloud: Fri Jun 2 10:25:45 UTC 2023

Browse source
This commit is contained in:
Automated 2023-06-02 10:25:45 +00:00
parent d0919dce4f
commit daa9cea776
199 changed files with 7828 additions and 401 deletions
Download patch file Download diff file Expand all files Collapse all files

8
gcloud/scc/findings/create
View file

@ -89,9 +89,11 @@ REQUIRED FLAGS
XSS_SCRIPTING
--event-time=EVENT_TIME
Time at which the issue is detected or the finding is created, in the
following format: YYYY-MM-DDThh:mm:ss.ffffffZ. Example:
2023-01-11T07:00:06.861Z
Time at which the event took place. For example, if the finding
represents an open firewall it would capture the time the open firewall
was detected. If event-time is not provided, it will default to UTC
version of NOW. See $ gcloud topic datetimes for information on
supported time formats.
--resource-name=RESOURCE_NAME
Full resource name of the Google Cloud Platform resource this finding

46
gcloud/scc/findings/group
View file

@ -69,27 +69,34 @@ POSITIONAL ARGUMENTS
FLAGS
--compare-duration=COMPARE_DURATION
When compare_duration is set, the GroupResult's "state_change"
attribute is updated to indicate whether the finding had its state
changed, the finding's state remained unchanged, or if the finding was
added during the compare_duration period of time that precedes the
read_time. This is the time between (read_time - compare_duration) and
read_time. The state_change value is derived based on the presence and
state of the finding at the two points in time. Intermediate state
changes between the two times don't affect the result. For example, the
results aren't affected if the finding is made inactive and then active
again. Possible "state_change" values when compare_duration is
specified:
When compare_duration is set, the result's "state_change" attribute is
updated to indicate whether the finding had its state changed, the
finding's state remained unchanged, or if the finding was added during
the compare_duration period of time that precedes the read_time. This
is the time between (read_time - compare_duration) and read_time. The
state_change value is derived based on the presence and state of the
finding at the two points in time. Intermediate state changes between
the two times don't affect the result. For example, the results aren't
affected if the finding is made inactive and then active again.
Possible "state_change" values when compare_duration is specified:
◆ 'CHANGED': indicates that the finding was present at the start of
compare_duration, but changed its state at read_time.
◆ 'UNCHANGED': indicates that the finding was present at the start of
compare_duration and did not change state at read_time.
◆ 'ADDED': indicates that the finding was not present at the start of
compare_duration, but was present at read_time. If compare_duration
is not specified, then the only possible state_change is "UNUSED",
which will be the state_change set for all findings present at
read_time. If this field is set then 'state_change' must be a
specified field in 'group_by'.
compare_duration, but was present at read_time.
◆ 'REMOVED': indicates that the finding was present at the start of
compare_duration, but was not present at read_time.
If compare_duration is not specified, then the only possible
state_change is 'UNUSED', which will be the state_change set for all
findings present at read_time. If this field is set then 'state_change'
must be a specified field in 'group_by'. See $ gcloud topic datetimes
for information on supported duration formats.
--filter=FILTER
Expression that defines the filter to apply across findings. The
@ -130,10 +137,9 @@ FLAGS
explicitly or let gcloud fetch one-page-at-a-time.
--read-time=READ_TIME
Time used as a reference point when filtering findings. The filter is
limited to findings existing at the supplied time and their values are
those at that specific time. For example. 2019-02-28T07:00:00Z. Absence
of this field will default to the API's version of NOW.
Time used as a reference point when filtering. Absence of this field
will default to the API's version of NOW. See $ gcloud topic datetimes
for information on supported time formats.
--source=SOURCE; default="-"
Source id. Defaults to all sources.

40
gcloud/scc/findings/list
View file

@ -78,24 +78,34 @@ POSITIONAL ARGUMENTS
FLAGS
--compare-duration=COMPARE_DURATION
ListFindingsResult's "state_change" attribute is updated to indicate
whether the finding had its state changed, the finding's state remained
unchanged, or if the finding was added in any state during the
compare_duration period of time that precedes the read_time. This is
the time between (read_time - compare_duration) and read_time. The
When compare_duration is set, the result's "state_change" attribute is
updated to indicate whether the finding had its state changed, the
finding's state remained unchanged, or if the finding was added during
the compare_duration period of time that precedes the read_time. This
is the time between (read_time - compare_duration) and read_time. The
state_change value is derived based on the presence and state of the
finding at the two points in time. Intermediate state changes between
the two times don't affect the result. For example, the results aren't
affected if the finding is made inactive and then active again.
Possible "state_change" values when compare_duration is specified:
"CHANGED" indicates that the finding was present at the start of
compare_duration, but changed its state at read_time. "UNCHANGED"
indicates that the finding was present at the start of compare_duration
and did not change state at read_time. "ADDED" indicates that the
finding was not present at the start of compare_duration, but was
present at read_time. If compare_duration is not specified, then the
only possible state_change is "UNUSED", which will be the state_change
set for all findings present at read_time. Example duration: "100000s"
◆ 'CHANGED': indicates that the finding was present at the start of
compare_duration, but changed its state at read_time.
◆ 'UNCHANGED': indicates that the finding was present at the start of
compare_duration and did not change state at read_time.
◆ 'ADDED': indicates that the finding was not present at the start of
compare_duration, but was present at read_time.
◆ 'REMOVED': indicates that the finding was present at the start of
compare_duration, but was not present at read_time.
If compare_duration is not specified, then the only possible
state_change is 'UNUSED', which will be the state_change set for all
findings present at read_time. If this field is set then 'state_change'
must be a specified field in 'group_by'. See $ gcloud topic datetimes
for information on supported duration formats.
--field-mask=FIELD_MASK
Field mask to specify the finding fields listed in the response. An
@ -124,8 +134,8 @@ FLAGS
--read-time=READ_TIME
Time used as a reference point when filtering. Absence of this field
will default to the API's version of NOW. For example --read-time
"2019-02-28T07:00:00Z"
will default to the API's version of NOW. See $ gcloud topic datetimes
for information on supported time formats.
--source=SOURCE; default="-"
Source id. Defaults to all sources.

4
gcloud/scc/findings/list-marks
View file

@ -79,8 +79,8 @@ FLAGS
--read-time=READ_TIME
Time used as a reference point when filtering. Absence of this field
will default to the API's version of NOW. For example --read-time
"2019-02-28T07:00:00Z"
will default to the API's version of NOW. See $ gcloud topic datetimes
for information on supported time formats.
LIST COMMAND FLAGS
--filter=EXPRESSION

3
gcloud/scc/findings/update
View file

@ -88,7 +88,8 @@ FLAGS
Time at which the event took place. For example, if the finding
represents an open firewall it would capture the time the open firewall
was detected. If event-time is not provided, it will default to UTC
version of NOW. For example 2019-02-28T07:00:00Z
version of NOW. See $ gcloud topic datetimes for information on
supported time formats.
--external-uri=EXTERNAL_URI
URI that, if available, points to a web page outside of Cloud SCC

4
gcloud/scc/findings/update-marks
View file

@ -92,8 +92,8 @@ FLAGS
--security-marks="key1=val1,key2=val2".
--start-time=START_TIME
Time at which the updated SecurityMarks take effect. For example:
2019-02-28T07:00:00Z
Time at which the updated SecurityMarks take effect. See $ gcloud topic
datetimes for information on supported time formats.
--update-mask=UPDATE_MASK
Use update-mask if you want to selectively update marks represented by