@@ -435,27 +435,39 @@ class GroupFindingsRequest(proto.Message):
435435
436436 - event_time: ``=``, ``>``, ``<``, ``>=``, ``<=``
437437
438- - severity: ``=``, ``:``
439-
440438 Usage: This should be milliseconds since epoch or an
441439 RFC3339 string. Examples:
442440 ``event_time = "2019-06-10T16:07:18-07:00"``
443441 ``event_time = 1560208038000``
444442
443+ - severity: ``=``, ``:``
444+
445+ - workflow_state: ``=``, ``:``
446+
445447 - security_marks.marks: ``=``, ``:``
446448
447449 - source_properties: ``=``, ``:``, ``>``, ``<``, ``>=``,
448450 ``<=``
449451
450- For example, ``source_properties.size = 100`` is a valid
451- filter string.
452+ For example, ``source_properties.size = 100`` is a valid
453+ filter string.
452454
453- Use a partial match on the empty string to filter based on a
454- property existing: ``source_properties.my_property : ""``
455+ Use a partial match on the empty string to filter based
456+ on a property existing:
457+ ``source_properties.my_property : ""``
455458
456- Use a negated partial match on the empty string to filter
457- based on a property not existing:
458- ``-source_properties.my_property : ""``
459+ Use a negated partial match on the empty string to filter
460+ based on a property not existing:
461+ ``-source_properties.my_property : ""``
462+
463+ - resource:
464+
465+ - resource.name: ``=``, ``:``
466+ - resource.parent_name: ``=``, ``:``
467+ - resource.parent_display_name: ``=``, ``:``
468+ - resource.project_name: ``=``, ``:``
469+ - resource.project_display_name: ``=``, ``:``
470+ - resource.type: ``=``, ``:``
459471 group_by (str):
460472 Required. Expression that defines what assets fields to use
461473 for grouping (including ``state_change``). The string value
@@ -958,25 +970,40 @@ class ListFindingsRequest(proto.Message):
958970
959971 - event_time: ``=``, ``>``, ``<``, ``>=``, ``<=``
960972
961- - severity: ``=``, ``:``
962-
963973 Usage: This should be milliseconds since epoch or an
964974 RFC3339 string. Examples:
965975 ``event_time = "2019-06-10T16:07:18-07:00"``
966976 ``event_time = 1560208038000``
967977
968- security_marks.marks: ``=``, ``:`` source_properties: ``=``,
969- ``:``, ``>``, ``<``, ``>=``, ``<=``
978+ - severity: ``=``, ``:``
970979
971- For example, ``source_properties.size = 100`` is a valid
972- filter string.
980+ - workflow_state: ``=``, ``:``
973981
974- Use a partial match on the empty string to filter based on a
975- property existing: ``source_properties.my_property : ""``
982+ - security_marks.marks: ``=``, ``:``
976983
977- Use a negated partial match on the empty string to filter
978- based on a property not existing:
979- ``-source_properties.my_property : ""``
984+ - source_properties: ``=``, ``:``, ``>``, ``<``, ``>=``,
985+ ``<=``
986+
987+ For example, ``source_properties.size = 100`` is a valid
988+ filter string.
989+
990+ Use a partial match on the empty string to filter based
991+ on a property existing:
992+ ``source_properties.my_property : ""``
993+
994+ Use a negated partial match on the empty string to filter
995+ based on a property not existing:
996+ ``-source_properties.my_property : ""``
997+
998+ - resource:
999+
1000+ - resource.name: ``=``, ``:``
1001+ - resource.parent_name: ``=``, ``:``
1002+ - resource.parent_display_name: ``=``, ``:``
1003+ - resource.project_name: ``=``, ``:``
1004+ - resource.project_display_name: ``=``, ``:``
1005+ - resource.type: ``=``, ``:``
1006+ - resource.folders.resource_folder: ``=``, ``:``
9801007 order_by (str):
9811008 Expression that defines what fields and order to use for
9821009 sorting. The string value should follow SQL syntax: comma
0 commit comments