google-apis-eventarc_v1 0.55.0 → 0.56.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ebf0cc7b44a764b06d9f49a7d61a44d955ef8a7cb98bcd5c2b6237b7d0e1c209
-  data.tar.gz: 2c02b9c4c45d56911cf7d9f974a45156c8461f79522ca2f5a9d3be7c2dd780e1
+  metadata.gz: ad3d14ff96c115544d2bc9389de8b80e5fc055e2c54bc017d469798847d8c763
+  data.tar.gz: c76823d8b05c894b622c951292993e7273ebca1c0982e74480c7991c9c7e0f2f
 SHA512:
-  metadata.gz: 0d8e4643904a2e5bbd5abd5cb4939b79c4aebf96b5d661e39eef3bc567134b2a84b4d5f1ef69f619f983f634c8ed5e23aa1b10b5013bcaf6447595c5705f03be
-  data.tar.gz: 67787bb0d666ef5ea2c7d681ba6388fa859fb120696747969b8c0105b2f6b5e7f334f907731e2a326b312ae09335f4442a1fa25f318a069a9e3d4e5461a255a1
+  metadata.gz: b59f416a0c69a467d14e3c726a50ac1444a8e96f75d123a4e47d0eb28c39bf52c0ad8efe2ee9e51e5d9eca2374a36d081962738d14b0ddcfcd23135a908b875f
+  data.tar.gz: 560efaee3e41fb09df73de71db0c9b355efe29efb623c0ee1280e50de4af7fafea7ee8fa928f1b9b48e498d6d48e7fab233e57f4905fc96cac4a551ba9b7b680

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-eventarc_v1
 
+### v0.56.0 (2024-11-10)
+
+* Regenerated from discovery document revision 20241029
+
 ### v0.55.0 (2024-11-03)
 
 * Regenerated from discovery document revision 20241021

data/lib/google/apis/eventarc_v1/classes.rb

@@ -993,10 +993,10 @@ module Google
         # Required. Service account email used to generate the [OAuth token](https://
         # developers.google.com/identity/protocols/OAuth2). The principal who calls this
         # API must have iam.serviceAccounts.actAs permission in the service account. See
-        # https://cloud.google.com/iam/docs/understanding-service-accounts?hl=en#
-        # sa_common for more information. Eventarc service agents must have roles/roles/
-        # iam.serviceAccountTokenCreator role to allow Pipeline to create OAuth2 tokens
-        # for authenticated requests.
+        # https://cloud.google.com/iam/docs/understanding-service-accounts for more
+        # information. Eventarc service agents must have roles/roles/iam.
+        # serviceAccountTokenCreator role to allow Pipeline to create OAuth2 tokens for
+        # authenticated requests.
         # Corresponds to the JSON property `serviceAccount`
         # @return [String]
         attr_accessor :service_account
@@ -1028,9 +1028,9 @@ module Google
         # Required. Service account email used to generate the OIDC Token. The principal
         # who calls this API must have iam.serviceAccounts.actAs permission in the
         # service account. See https://cloud.google.com/iam/docs/understanding-service-
-        # accounts?hl=en#sa_common for more information. Eventarc service agents must
-        # have roles/roles/iam.serviceAccountTokenCreator role to allow the Pipeline to
-        # create OpenID tokens for authenticated requests.
+        # accounts for more information. Eventarc service agents must have roles/roles/
+        # iam.serviceAccountTokenCreator role to allow the Pipeline to create OpenID
+        # tokens for authenticated requests.
         # Corresponds to the JSON property `serviceAccount`
         # @return [String]
         attr_accessor :service_account
@@ -1050,78 +1050,109 @@ module Google
       class GoogleCloudEventarcV1PipelineDestinationHttpEndpoint
         include Google::Apis::Core::Hashable
       
-        # Optional. The CEL expression used to construct a new HTTP request to be sent
-        # to the final destination. The result of the CEL expression must be a map of
-        # key/value pairs such that: - If a map named `headers` exists on the result of
-        # the expression, then its key/value pairs are directly mapped to the HTTP
-        # request headers. The headers values are constructed from the corresponding
-        # value type’s canonical representation. If the `headers` field doesn’t exist
-        # then the resulting HTTP request will be without headers. - If a field named `
-        # body` exists on the result of the expression then its value is directly mapped
-        # to the body of the request. If the value of the `body` field is of type bytes
-        # or string then it is used for the HTTP request body as-is, with no conversion.
-        # If the body field is of any other type then it is converted to a JSON string.
-        # If the body field doesn’t exist then the resulting HTTP request will be
-        # without a body. - Any other fields in the resulting expression will be ignored.
-        # The CEL expression may access the incoming CloudEvent message in its
+        # Optional. The CEL expression used to modify how the destination-bound HTTP
+        # request is constructed. If a binding expression is not specified here, the
+        # message is treated as a CloudEvent and is mapped to the HTTP request according
+        # to the CloudEvent HTTP Protocol Binding Binary Content Mode. In this
+        # representation, all fields except the `data` and `datacontenttype` field on
+        # the message are mapped to HTTP request headers with a prefix of `ce-`. To
+        # construct the HTTP request payload and the value of the content-type HTTP
+        # header, the payload format is defined as follows: 1) Use the
+        # output_payload_format_type on the Pipeline.Destination if it is set, else: 2)
+        # Use the input_payload_format_type on the Pipeline if it is set, else: 3) Treat
+        # the payload as opaque binary data. The `data` field of the message is
+        # converted to the payload format or left as-is for case 3) and then attached as
+        # the payload of the HTTP request. The `content-type` header on the HTTP request
+        # is set to the payload format type or left empty for case 3). However, if a
+        # mediation has updated the `datacontenttype` field on the message so that it is
+        # not the same as the payload format type but it is still a prefix of the
+        # payload format type, then the `content-type` header on the HTTP request is set
+        # to this `datacontenttype` value. For example, if the `datacontenttype` is "
+        # application/json" and the payload format type is "application/json; charset=
+        # utf-8", then the `content-type` header on the HTTP request is set to "
+        # application/json; charset=utf-8". If a non-empty binding expression is
+        # specified then this expression is used to modify the default CloudEvent HTTP
+        # Protocol Binding Binary Content representation. The result of the CEL
+        # expression must be a map of key/value pairs which is used as follows: - If a
+        # map named `headers` exists on the result of the expression, then its key/value
+        # pairs are directly mapped to the HTTP request headers. The headers values are
+        # constructed from the corresponding value type's canonical representation. If
+        # the `headers` field doesn't exist then the resulting HTTP request will be the
+        # headers of the CloudEvent HTTP Binding Binary Content Mode representation of
+        # the final message. Note: If the specified binding expression, has updated the `
+        # datacontenttype` field on the message so that it is not the same as the
+        # payload format type but it is still a prefix of the payload format type, then
+        # the `content-type` header in the `headers` map is set to this `datacontenttype`
+        # value. - If a field named `body` exists on the result of the expression then
+        # its value is directly mapped to the body of the request. If the value of the `
+        # body` field is of type bytes or string then it is used for the HTTP request
+        # body as-is, with no conversion. If the body field is of any other type then it
+        # is converted to a JSON string. If the body field does not exist then the
+        # resulting payload of the HTTP request will be data value of the CloudEvent
+        # HTTP Binding Binary Content Mode representation of the final message as
+        # described earlier. - Any other fields in the resulting expression will be
+        # ignored. The CEL expression may access the incoming CloudEvent message in its
         # definition, as follows: - The `data` field of the incoming CloudEvent message
-        # can be accessed using the `message.data` value. - Each attribute of the
-        # incoming CloudEvent message can be accessed using the `message.` value, where
-        # is replaced with the name of the attribute. Headers added to the request by
-        # previous filters in the chain can be accessed in the CEL expression using the `
-        # headers` variable. The `headers` variable defines a map of key/value pairs
-        # corresponding to the HTTP headers added by previous mediation steps and not
-        # the headers present on the original incoming request. For example, the
-        # following CEL expression can be used to construct a Headers-only HTTP request
-        # by adding an additional header to the headers added by previous mediations in
-        # the Pipeline: ``` `"headers": headers.merge(`"new-header-key": "new-header-
-        # value"`)` ``` Additionally, the following CEL extension functions are provided
-        # for use in this CEL expression: - toBase64Url: map.toBase64Url() -> string -
-        # Converts a CelValue to a base64url encoded string - toJsonString: map.
-        # toJsonString() -> string - Converts a CelValue to a JSON string - merge: map1.
-        # merge(map2) -> map3 - Merges the passed CEL map with the existing CEL map the
-        # function is applied to. - If the same key exists in both maps, if the key's
-        # value is type map both maps are merged else the value from the passed map is
-        # used. - toMap: list(map).toMap() -> map - Converts a CEL list of CEL maps to a
-        # single CEL map - toDestinationPayloadFormat(): message.data.
-        # toDestinationPayloadFormat() -> string or bytes - Converts the message data to
-        # the destination payload format specified in Pipeline.Destination.
-        # output_payload_format - This function is meant to be applied to the message.
-        # data field. - If the destination payload format is not set, the function will
-        # return the message data unchanged. - toCloudEventJsonWithPayloadFormat:
-        # message.toCloudEventJsonWithPayloadFormat() -> map - Converts a message to the
-        # corresponding structure of JSON format for CloudEvents - This function applies
-        # toDestinationPayloadFormat() to the message data. It also sets the
-        # corresponding datacontenttype of the CloudEvent, as indicated by Pipeline.
-        # Destination.output_payload_format. If no output_payload_format is set it will
-        # use the existing datacontenttype on the CloudEvent if present, else leave
-        # datacontenttype absent. - This function expects that the content of the
-        # message will adhere to the standard CloudEvent format. If it doesn’t then this
-        # function will fail. - The result is a CEL map that corresponds to the JSON
-        # representation of the CloudEvent. To convert that data to a JSON string it can
-        # be chained with the toJsonString function. If a binding is not specified here,
-        # by default the message is treated as a CloudEvent and is mapped to the HTTP
-        # request according to the CloudEvent HTTP Protocol Binding Binary Content Mode.
-        # The Pipeline converts the data field of the message to the format provided in
-        # Pipeline.Destination.output_payload_format and maps it to the body field of
-        # the result. It also sets the corresponding Content-Type header to the
-        # output_payload_format type. If the Pipeline.Destination.output_payload_format
-        # is not set, then the Pipeline will treat the data field of the message as
-        # opaque binary data and attach it to the request body as bytes. In this case
-        # the Content-type header will be set to the value of the datacontenttype
-        # attribute set on the incoming CloudEvent message if present and the `
-        # application/octet-stream` MIME type otherwise. The Pipeline expects that the
-        # content of the message will adhere to the standard CloudEvent format. If it
-        # doesn’t then the outgoing message request may fail with a persistent error.
+        # can be accessed using the `message.data` value. Subfields of `message.data`
+        # may also be accessed if an input_payload_format has been specified on the
+        # Pipeline. - Each attribute of the incoming CloudEvent message can be accessed
+        # using the `message.` value, where is replaced with the name of the attribute. -
+        # Existing headers can be accessed in the CEL expression using the `headers`
+        # variable. The `headers` variable defines a map of key/value pairs
+        # corresponding to the HTTP headers of the CloudEvent HTTP Binding Binary
+        # Content Mode representation of the final message as described earlier. For
+        # example, the following CEL expression can be used to construct an HTTP request
+        # by adding an additional header to the HTTP headers of the CloudEvent HTTP
+        # Binding Binary Content Mode representation of the final message and by
+        # overwriting the body of the request: ``` ` "headers": headers.merge(`"new-
+        # header-key": "new-header-value"`), "body": "new-body" ` ``` Additionally, the
+        # following CEL extension functions are provided for use in this CEL expression:
+        # - toBase64Url: map.toBase64Url() -> string - Converts a CelValue to a
+        # base64url encoded string - toJsonString: map.toJsonString() -> string -
+        # Converts a CelValue to a JSON string - merge: map1.merge(map2) -> map3 -
+        # Merges the passed CEL map with the existing CEL map the function is applied to.
+        # - If the same key exists in both maps, if the key's value is type map both
+        # maps are merged else the value from the passed map is used. - denormalize: map.
+        # denormalize() -> map - Denormalizes a CEL map such that every value of type
+        # map or key in the map is expanded to return a single level map. - The
+        # resulting keys are "." separated indices of the map keys. - For example: ` "a":
+        # 1, "b": ` "c": 2, "d": 3 ` "e": [4, 5] ` .denormalize() -> ` "a": 1, "b.c": 2,
+        # "b.d": 3, "e.0": 4, "e.1": 5 ` - setField: map.setField(key, value) ->
+        # message - Sets the field of the message with the given key to the given value.
+        # - If the field is not present it will be added. - If the field is present it
+        # will be overwritten. - The key can be a dot separated path to set a field in a
+        # nested message. - Key must be of type string. - Value may be any valid type. -
+        # removeFields: map.removeFields([key1, key2, ...]) -> message - Removes the
+        # fields of the map with the given keys. - The keys can be a dot separated path
+        # to remove a field in a nested message. - If a key is not found it will be
+        # ignored. - Keys must be of type string. - toMap: [map1, map2, ...].toMap() ->
+        # map - Converts a CEL list of CEL maps to a single CEL map -
+        # toDestinationPayloadFormat(): message.data.toDestinationPayloadFormat() ->
+        # string or bytes - Converts the message data to the destination payload format
+        # specified in Pipeline.Destination.output_payload_format - This function is
+        # meant to be applied to the message.data field. - If the destination payload
+        # format is not set, the function will return the message data unchanged. -
+        # toCloudEventJsonWithPayloadFormat: message.toCloudEventJsonWithPayloadFormat()
+        # -> map - Converts a message to the corresponding structure of JSON format for
+        # CloudEvents - This function applies toDestinationPayloadFormat() to the
+        # message data. It also sets the corresponding datacontenttype of the CloudEvent,
+        # as indicated by Pipeline.Destination.output_payload_format. If no
+        # output_payload_format is set it will use the existing datacontenttype on the
+        # CloudEvent if present, else leave datacontenttype absent. - This function
+        # expects that the content of the message will adhere to the standard CloudEvent
+        # format. If it doesn't then this function will fail. - The result is a CEL map
+        # that corresponds to the JSON representation of the CloudEvent. To convert that
+        # data to a JSON string it can be chained with the toJsonString function. The
+        # Pipeline expects that the message it receives adheres to the standard
+        # CloudEvent format. If it doesn't then the outgoing message request may fail
+        # with a persistent error.
         # Corresponds to the JSON property `messageBindingTemplate`
         # @return [String]
         attr_accessor :message_binding_template
       
         # Required. The URI of the HTTP enpdoint. The value must be a RFC2396 URI string.
-        # Examples: `http://10.10.10.8:80/route`, `http://svc.us-central1.p.local:8080/`
-        # . Only HTTP and HTTPS protocols are supported. The host can be either a static
-        # IP addressable from the VPC specified by the network config, or an internal
-        # DNS hostname of the service resolvable via Cloud DNS.
+        # Examples: `https://svc.us-central1.p.local:8080/route`. Only the HTTPS
+        # protocol is supported.
         # Corresponds to the JSON property `uri`
         # @return [String]
         attr_accessor :uri
@@ -1182,7 +1213,42 @@ module Google
       class GoogleCloudEventarcV1PipelineMediationTransformation
         include Google::Apis::Core::Hashable
       
-        # Optional. The template to apply to transform messages.
+        # Optional. The CEL expression template to apply to transform messages. The
+        # following CEL extension functions are provided for use in this CEL expression:
+        # - merge: map1.merge(map2) -> map3 - Merges the passed CEL map with the
+        # existing CEL map the function is applied to. - If the same key exists in both
+        # maps, if the key's value is type map both maps are merged else the value from
+        # the passed map is used. - denormalize: map.denormalize() -> map - Denormalizes
+        # a CEL map such that every value of type map or key in the map is expanded to
+        # return a single level map. - The resulting keys are "." separated indices of
+        # the map keys. - For example: ` "a": 1, "b": ` "c": 2, "d": 3 ` "e": [4, 5] ` .
+        # denormalize() -> ` "a": 1, "b.c": 2, "b.d": 3, "e.0": 4, "e.1": 5 ` - setField:
+        # map.setField(key, value) -> message - Sets the field of the message with the
+        # given key to the given value. - If the field is not present it will be added. -
+        # If the field is present it will be overwritten. - The key can be a dot
+        # separated path to set a field in a nested message. - Key must be of type
+        # string. - Value may be any valid type. - removeFields: map.removeFields([key1,
+        # key2, ...]) -> message - Removes the fields of the map with the given keys. -
+        # The keys can be a dot separated path to remove a field in a nested message. -
+        # If a key is not found it will be ignored. - Keys must be of type string. -
+        # toMap: [map1, map2, ...].toMap() -> map - Converts a CEL list of CEL maps to a
+        # single CEL map - toDestinationPayloadFormat(): message.data.
+        # toDestinationPayloadFormat() -> string or bytes - Converts the message data to
+        # the destination payload format specified in Pipeline.Destination.
+        # output_payload_format - This function is meant to be applied to the message.
+        # data field. - If the destination payload format is not set, the function will
+        # return the message data unchanged. - toCloudEventJsonWithPayloadFormat:
+        # message.toCloudEventJsonWithPayloadFormat() -> map - Converts a message to the
+        # corresponding structure of JSON format for CloudEvents - This function applies
+        # toDestinationPayloadFormat() to the message data. It also sets the
+        # corresponding datacontenttype of the CloudEvent, as indicated by Pipeline.
+        # Destination.output_payload_format. If no output_payload_format is set it will
+        # use the existing datacontenttype on the CloudEvent if present, else leave
+        # datacontenttype absent. - This function expects that the content of the
+        # message will adhere to the standard CloudEvent format. If it doesn't then this
+        # function will fail. - The result is a CEL map that corresponds to the JSON
+        # representation of the CloudEvent. To convert that data to a JSON string it can
+        # be chained with the toJsonString function.
         # Corresponds to the JSON property `transformationTemplate`
         # @return [String]
         attr_accessor :transformation_template
@@ -1296,13 +1362,13 @@ module Google
         attr_accessor :max_attempts
       
         # Optional. The maximum amount of seconds to wait between retry attempts. The
-        # value must be between 0 and 600. The default value for this field is 60.
+        # value must be between 1 and 600. The default value for this field is 60.
         # Corresponds to the JSON property `maxRetryDelay`
         # @return [String]
         attr_accessor :max_retry_delay
       
         # Optional. The minimum amount of seconds to wait between retry attempts. The
-        # value must be between 0 and 600. The default value for this field is 5.
+        # value must be between 1 and 600. The default value for this field is 5.
         # Corresponds to the JSON property `minRetryDelay`
         # @return [String]
         attr_accessor :min_retry_delay

data/lib/google/apis/eventarc_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module EventarcV1
       # Version of the google-apis-eventarc_v1 gem
-      GEM_VERSION = "0.55.0"
+      GEM_VERSION = "0.56.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.15.1"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20241021"
+      REVISION = "20241029"
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-eventarc_v1
 version: !ruby/object:Gem::Version
-  version: 0.55.0
+  version: 0.56.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-11-03 00:00:00.000000000 Z
+date: 2024-11-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-eventarc_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-eventarc_v1/v0.55.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-eventarc_v1/v0.56.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-eventarc_v1
 post_install_message: 
 rdoc_options: []
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.21
+rubygems_version: 3.5.22
 signing_key: 
 specification_version: 4
 summary: Simple REST client for Eventarc API V1