service.rb in google-api-client-0.53.0

- old
+ new

@@ -370,20 +370,20 @@
         #   security_marks.marks.marka The supported operators are: * `=` for all value
         #   types. * `>`, `<`, `>=`, `<=` for integer values. * `:`, meaning substring
         #   matching, for strings. The supported value types are: * string literals in
         #   quotes. * integer literals without quotes. * boolean literals `true` and `
         #   false` without quotes. The following field and operator combinations are
-        #   supported: name: `=` parent: `=`, `:` resource_name: `=`, `:` state: `=`, `:`
-        #   category: `=`, `:` external_uri: `=`, `:` event_time: `=`, `>`, `<`, `>=`, `<=`
-        #   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: `=`, `:`, `>`, `<`, `>=`, `<=
-        #   ` 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 : ""`
+        #   supported: * name: `=` * parent: `=`, `:` * resource_name: `=`, `:` * state: `=
+        #   `, `:` * category: `=`, `:` * external_uri: `=`, `:` * 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: `=`, `:`, `>`, `<`, `>=`, `<=` 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 : ""`
         # @param [String] order_by
         #   Expression that defines what fields and order to use for sorting. The string
         #   value should follow SQL syntax: comma separated list of fields. For example: "
         #   name,resource_properties.a_property". The default sorting order is ascending.
         #   To specify descending order for a field, a suffix " desc" should be appended
@@ -1563,20 +1563,20 @@
         #   security_marks.marks.marka The supported operators are: * `=` for all value
         #   types. * `>`, `<`, `>=`, `<=` for integer values. * `:`, meaning substring
         #   matching, for strings. The supported value types are: * string literals in
         #   quotes. * integer literals without quotes. * boolean literals `true` and `
         #   false` without quotes. The following field and operator combinations are
-        #   supported: name: `=` parent: `=`, `:` resource_name: `=`, `:` state: `=`, `:`
-        #   category: `=`, `:` external_uri: `=`, `:` event_time: `=`, `>`, `<`, `>=`, `<=`
-        #   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: `=`, `:`, `>`, `<`, `>=`, `<=
-        #   ` 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 : ""`
+        #   supported: * name: `=` * parent: `=`, `:` * resource_name: `=`, `:` * state: `=
+        #   `, `:` * category: `=`, `:` * external_uri: `=`, `:` * 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: `=`, `:`, `>`, `<`, `>=`, `<=` 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 : ""`
         # @param [String] order_by
         #   Expression that defines what fields and order to use for sorting. The string
         #   value should follow SQL syntax: comma separated list of fields. For example: "
         #   name,resource_properties.a_property". The default sorting order is ascending.
         #   To specify descending order for a field, a suffix " desc" should be appended
@@ -2076,19 +2076,19 @@
         #   security_marks.marks.marka The supported operators are: * `=` for all value
         #   types. * `>`, `<`, `>=`, `<=` for integer values. * `:`, meaning substring
         #   matching, for strings. The supported value types are: * string literals in
         #   quotes. * integer literals without quotes. * boolean literals `true` and `
         #   false` without quotes. The following field and operator combinations are
-        #   supported: name: `=` parent: `=`, `:` resource_name: `=`, `:` state: `=`, `:`
-        #   category: `=`, `:` external_uri: `=`, `:` event_time: `=`, `>`, `<`, `>=`, `<=`
-        #   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: `=`, `:`, `>`, `<`, `>=`, `<=
-        #   ` 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 : ""`
+        #   supported: * name: `=` * parent: `=`, `:` * resource_name: `=`, `:` * state: `=
+        #   `, `:` * category: `=`, `:` * external_uri: `=`, `:` * 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: `=`, `:`, `>`, `<`, `>=`, `<=` 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 : ""`
         # @param [String] order_by
         #   Expression that defines what fields and order to use for sorting. The string
         #   value should follow SQL syntax: comma separated list of fields. For example: "
         #   name,resource_properties.a_property". The default sorting order is ascending.
         #   To specify descending order for a field, a suffix " desc" should be appended