google-apis-chat_v1 0.75.0 → 0.76.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 183fb543dee3e1ee0f9f0004a8706751c546a705090014c6b41431ad547d37f7
-  data.tar.gz: a829aada3ccacf1969f6335fed58d060835e53aaf11bbbdb2e8c97b24e9e7d7b
+  metadata.gz: 005d8d6c7edccdf3a114dc00ab25d5d87789bf2d339adbcb6dd1a22c5a2521bc
+  data.tar.gz: 2bc9dd91af3f1fa65a1aef505c3c559c74feb7833406f2eb6f7a39488366f235
 SHA512:
-  metadata.gz: 185953c34071ca1cd087a7f0efad86518aea3273e7b7bfab29437b27e7085a08f7ff47fff6cde07e69fb6e4363da16115c674b1c080cf45716803ca2ef33d370
-  data.tar.gz: d329b2e79138c07984a467a7a6f4d3516f2fe102f4c69a0f7fc0301eef038f088021e29ccd1a97f24fd0f39cf9151ba1ca20b251158dae14e8c658ed034bebde
+  metadata.gz: 8368649471a5a787712aa3489c45c75c44fa6e3a31c67c8cc9582a0bb39874f15f5304f7d2690d23b9a407064684e2484edd77dd651788a75557594421e57165
+  data.tar.gz: 8459f904c2300ca2d60bcb2dc504df35a6869f1a8904a76909d103f0089f7cad01af39cddf737b1591586d567bd40d13c53008f6398df7286a99ea8c88e4e6dd

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-chat_v1
 
+### v0.76.0 (2023-11-19)
+
+* Regenerated from discovery document revision 20231114
+
 ### v0.75.0 (2023-11-12)
 
 * Regenerated from discovery document revision 20231105

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

@@ -4163,17 +4163,16 @@ module Google
       
         # Resource name for a Google Chat user. Format: `users/`user``. `users/app` can
         # be used as an alias for the calling app bot user. For human users, ``user`` is
-        # the same user identifier as: - the ``person_id`` for the [Person](https://
-        # developers.google.com/people/api/rest/v1/people) in the People API, where the
-        # Person `resource_name` is `people/`person_id``. For example, `users/123456789`
-        # in Chat API represents the same person as `people/123456789` in People API. -
-        # the `id` for a [user](https://developers.google.com/admin-sdk/directory/
-        # reference/rest/v1/users) in the Admin SDK Directory API. - the user's email
-        # address can be used as an alias for ``user`` in API requests. For example, if
-        # the People API Person `resourceName` for `user@example.com` is `people/
-        # 123456789`, you can use `users/user@example.com` as an alias to reference `
-        # users/123456789`. Only the canonical resource name (for example `users/
-        # 123456789`) will be returned from the API.
+        # the same user identifier as: - the `id` for the [Person](https://developers.
+        # google.com/people/api/rest/v1/people) in the People API. For example, `users/
+        # 123456789` in Chat API represents the same person as the `123456789` Person
+        # profile ID in People API. - the `id` for a [user](https://developers.google.
+        # com/admin-sdk/directory/reference/rest/v1/users) in the Admin SDK Directory
+        # API. - the user's email address can be used as an alias for ``user`` in API
+        # requests. For example, if the People API Person profile ID for `user@example.
+        # com` is `123456789`, you can use `users/user@example.com` as an alias to
+        # reference `users/123456789`. Only the canonical resource name (for example `
+        # users/123456789`) will be returned from the API.
         # Corresponds to the JSON property `name`
         # @return [String]
         attr_accessor :name

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

@@ -16,13 +16,13 @@ module Google
   module Apis
     module ChatV1
       # Version of the google-apis-chat_v1 gem
-      GEM_VERSION = "0.75.0"
+      GEM_VERSION = "0.76.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.12.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20231105"
+      REVISION = "20231114"
     end
   end
 end

data/lib/google/apis/chat_v1/service.rb

@@ -227,15 +227,15 @@ module Google
         # auth/service-accounts).
         # @param [String] name
         #   Required. Resource name of the user to find direct message with. Format: `
-        #   users/`user``, where ``user`` is either the ``person_id`` for the [person](
-        #   https://developers.google.com/people/api/rest/v1/people) from the People API,
-        #   or the `id` for the [user](https://developers.google.com/admin-sdk/directory/
-        #   reference/rest/v1/users) in the Directory API. For example, if the People API `
-        #   Person.resourceName` is `people/123456789`, you can find a direct message with
-        #   that person by using `users/123456789` as the `name`. When [authenticated as a
-        #   user](https://developers.google.com/chat/api/guides/auth/users), you can use
-        #   the email as an alias for ``user``. For example, `users/example@gmail.com`
-        #   where `example@gmail.com` is the email of the Google Chat user.
+        #   users/`user``, where ``user`` is either the `id` for the [person](https://
+        #   developers.google.com/people/api/rest/v1/people) from the People API, or the `
+        #   id` for the [user](https://developers.google.com/admin-sdk/directory/reference/
+        #   rest/v1/users) in the Directory API. For example, if the People API profile ID
+        #   is `123456789`, you can find a direct message with that person by using `users/
+        #   123456789` as the `name`. When [authenticated as a user](https://developers.
+        #   google.com/chat/api/guides/auth/users), you can use the email as an alias for `
+        #   `user``. For example, `users/example@gmail.com` where `example@gmail.com` is
+        #   the email of the Google Chat user.
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user
@@ -427,27 +427,27 @@ module Google
         # add memberships with the appropriate `member.name` in the `SetUpSpaceRequest`.
         # To add a human user, use `users/`user``, where ``user`` can be the email
         # address for the user. For users in the same Workspace organization ``user``
-        # can also be the ``person_id`` for the person from the People API, or the `id`
-        # for the user in the Directory API. For example, if the People API Person `
-        # resourceName` for `user@example.com` is `people/123456789`, you can add the
-        # user to the space by setting the `membership.member.name` to `users/user@
-        # example.com` or `users/123456789`. For a space or group chat, if the caller
-        # blocks or is blocked by some members, then those members aren't added to the
-        # created space. To create a direct message (DM) between the calling user and
-        # another human user, specify exactly one membership to represent the human user.
-        # If one user blocks the other, the request fails and the DM isn't created. To
-        # create a DM between the calling user and the calling app, set `Space.
-        # singleUserBotDm` to `true` and don't specify any memberships. You can only use
-        # this method to set up a DM with the calling app. To add the calling app as a
-        # member of a space or an existing DM between two human users, see [create a
-        # membership](https://developers.google.com/chat/api/guides/v1/members/create).
-        # If a DM already exists between two users, even when one user blocks the other
-        # at the time a request is made, then the existing DM is returned. Spaces with
-        # threaded replies aren't supported. If you receive the error message `
-        # ALREADY_EXISTS` when setting up a space, try a different `displayName`. An
-        # existing space within the Google Workspace organization might already use this
-        # display name. Requires [user authentication](https://developers.google.com/
-        # chat/api/guides/auth/users).
+        # can also be the `id` for the person from the People API, or the `id` for the
+        # user in the Directory API. For example, if the People API Person profile ID
+        # for `user@example.com` is `123456789`, you can add the user to the space by
+        # setting the `membership.member.name` to `users/user@example.com` or `users/
+        # 123456789`. For a space or group chat, if the caller blocks or is blocked by
+        # some members, then those members aren't added to the created space. To create
+        # a direct message (DM) between the calling user and another human user, specify
+        # exactly one membership to represent the human user. If one user blocks the
+        # other, the request fails and the DM isn't created. To create a DM between the
+        # calling user and the calling app, set `Space.singleUserBotDm` to `true` and
+        # don't specify any memberships. You can only use this method to set up a DM
+        # with the calling app. To add the calling app as a member of a space or an
+        # existing DM between two human users, see [create a membership](https://
+        # developers.google.com/chat/api/guides/v1/members/create). If a DM already
+        # exists between two users, even when one user blocks the other at the time a
+        # request is made, then the existing DM is returned. Spaces with threaded
+        # replies aren't supported. If you receive the error message `ALREADY_EXISTS`
+        # when setting up a space, try a different `displayName`. An existing space
+        # within the Google Workspace organization might already use this display name.
+        # Requires [user authentication](https://developers.google.com/chat/api/guides/
+        # auth/users).
         # @param [Google::Apis::ChatV1::SetUpSpaceRequest] set_up_space_request_object
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
@@ -489,11 +489,11 @@ module Google
         # app to a space or a direct message between two human users, use `users/app`.
         # Unable to add other apps to the space. - To add a human user, use `users/`user`
         # `, where ``user`` can be the email address for the user. For users in the same
-        # Workspace organization ``user`` can also be the ``person_id`` for the person
-        # from the People API, or the `id` for the user in the Directory API. For
-        # example, if the People API Person `resourceName` for `user@example.com` is `
-        # people/123456789`, you can add the user to the space by setting the `
-        # membership.member.name` to `users/user@example.com` or `users/123456789`.
+        # Workspace organization ``user`` can also be the `id` for the person from the
+        # People API, or the `id` for the user in the Directory API. For example, if the
+        # People API Person profile ID for `user@example.com` is `123456789`, you can
+        # add the user to the space by setting the `membership.member.name` to `users/
+        # user@example.com` or `users/123456789`.
         # @param [String] parent
         #   Required. The resource name of the space for which to create the membership.
         #   Format: spaces/`space`

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-chat_v1
 version: !ruby/object:Gem::Version
-  version: 0.75.0
+  version: 0.76.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-11-12 00:00:00.000000000 Z
+date: 2023-11-19 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-chat_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.75.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.76.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1
 post_install_message: 
 rdoc_options: []