Skip to content
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.

Commit

Permalink
docs: update currently supported Finding filter fields (#159)
Browse files Browse the repository at this point in the history
PiperOrigin-RevId: 378264900

Source-Link: googleapis/googleapis@020ba74

Source-Link: googleapis/googleapis-gen@b1413c1
  • Loading branch information
gcf-owl-bot[bot] committed Jun 10, 2021
1 parent 5cb992c commit 89ca24b
Show file tree
Hide file tree
Showing 2 changed files with 47 additions and 21 deletions.
1 change: 0 additions & 1 deletion .coveragerc
Expand Up @@ -2,7 +2,6 @@
branch = True

[report]
fail_under = 100
show_missing = True
omit =
google/cloud/securitycenter/__init__.py
Expand Down
67 changes: 47 additions & 20 deletions google/cloud/securitycenter_v1/types/securitycenter_service.py
Expand Up @@ -435,27 +435,39 @@ class GroupFindingsRequest(proto.Message):
- event_time: ``=``, ``>``, ``<``, ``>=``, ``<=``
- severity: ``=``, ``:``
Usage: This should be milliseconds since epoch or an
RFC3339 string. Examples:
``event_time = "2019-06-10T16:07:18-07:00"``
``event_time = 1560208038000``
- severity: ``=``, ``:``
- workflow_state: ``=``, ``:``
- security_marks.marks: ``=``, ``:``
- source_properties: ``=``, ``:``, ``>``, ``<``, ``>=``,
``<=``
For example, ``source_properties.size = 100`` is a valid
filter string.
For example, ``source_properties.size = 100`` is a valid
filter string.
Use a partial match on the empty string to filter based on a
property existing: ``source_properties.my_property : ""``
Use a partial match on the empty string to filter based
on a property existing:
``source_properties.my_property : ""``
Use a negated partial match on the empty string to filter
based on a property not existing:
``-source_properties.my_property : ""``
Use a negated partial match on the empty string to filter
based on a property not existing:
``-source_properties.my_property : ""``
- resource:
- resource.name: ``=``, ``:``
- resource.parent_name: ``=``, ``:``
- resource.parent_display_name: ``=``, ``:``
- resource.project_name: ``=``, ``:``
- resource.project_display_name: ``=``, ``:``
- resource.type: ``=``, ``:``
group_by (str):
Required. Expression that defines what assets fields to use
for grouping (including ``state_change``). The string value
Expand Down Expand Up @@ -958,25 +970,40 @@ class ListFindingsRequest(proto.Message):
- event_time: ``=``, ``>``, ``<``, ``>=``, ``<=``
- severity: ``=``, ``:``
Usage: This should be milliseconds since epoch or an
RFC3339 string. Examples:
``event_time = "2019-06-10T16:07:18-07:00"``
``event_time = 1560208038000``
security_marks.marks: ``=``, ``:`` source_properties: ``=``,
``:``, ``>``, ``<``, ``>=``, ``<=``
- severity: ``=``, ``:``
For example, ``source_properties.size = 100`` is a valid
filter string.
- workflow_state: ``=``, ``:``
Use a partial match on the empty string to filter based on a
property existing: ``source_properties.my_property : ""``
- security_marks.marks: ``=``, ``:``
Use a negated partial match on the empty string to filter
based on a property not existing:
``-source_properties.my_property : ""``
- source_properties: ``=``, ``:``, ``>``, ``<``, ``>=``,
``<=``
For example, ``source_properties.size = 100`` is a valid
filter string.
Use a partial match on the empty string to filter based
on a property existing:
``source_properties.my_property : ""``
Use a negated partial match on the empty string to filter
based on a property not existing:
``-source_properties.my_property : ""``
- resource:
- resource.name: ``=``, ``:``
- resource.parent_name: ``=``, ``:``
- resource.parent_display_name: ``=``, ``:``
- resource.project_name: ``=``, ``:``
- resource.project_display_name: ``=``, ``:``
- resource.type: ``=``, ``:``
- resource.folders.resource_folder: ``=``, ``:``
order_by (str):
Expression that defines what fields and order to use for
sorting. The string value should follow SQL syntax: comma
Expand Down

0 comments on commit 89ca24b

Please sign in to comment.