Contains an operation for a resource loosely based on the JSON-PATCH format with support for: - Custom filters for describing partial array patch. - Extended path values for describing nested arrays. - Custom fields for describing the resource for which the operation is being described. - Allows extension to custom operations not natively supported by RFC6902. See https://tools.ietf.org/html/rfc6902 for details on the original RFC.
Type of GCP resource being modified/tested. This field is always populated. Example: cloudresourcemanager.googleapis.com/Project, compute.googleapis.com/Instance
Path to the target field being operated on. If the operation is at the resource level, then path should be “/”. This field is always populated.
Can be set with action ‘copy’ or ‘move’ to indicate the source field within resource or source_resource, ignored if provided for other operation types.
Value for the path field. Will be set for
actions:‘add’/‘replace’. Maybe set for action: ‘test’. Either
this or value_matcher will be set for ‘test’ operation. An
exact match must be performed.
Set of filters to apply if path refers to array elements
or nested array elements in order to narrow down to a single
unique element that is being tested/modified. This is intended
to be an exact match per filter. To perform advanced matching,
use path_value_matchers. - Example: { “/versions/*/name" :
"it-123" "/versions/*/targetSize/percent”: 20 } - Example:
{ “/bindings//role": "roles/admin" "/bindings//condition”
: null } - Example: { "/bindings/*/role“:”roles/admin"
“/bindings/*/members/*” : [“x@google.com”, “y@google.com”]
} When both path_filters and path_value_matchers are set,
an implicit AND must be performed.
Classes
PathFiltersEntry
API documentation for recommender_v1beta1.types.Operation.PathFiltersEntry class.
PathValueMatchersEntry
API documentation for recommender_v1beta1.types.Operation.PathValueMatchersEntry class.