google-apis-chat_v1 0.96.0 → 0.98.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a1dd1b43ea4c68c96b77b979450786bbbb930db7607b5bc7755be03c6f148551
4
- data.tar.gz: 46d19e3452b5e13515410d67f74758a8fefe4172e6586aba3dfc7a22f9dc40cf
3
+ metadata.gz: 7c7f5381d0fb825bff8741b8e72d07ec79daf695a34ebb61c50f8056026393a4
4
+ data.tar.gz: 74e6bfcf2f7c125f2d9d535783d74b30912e314f5d7255f81a7e97b255b8632e
5
5
  SHA512:
6
- metadata.gz: 1c1a5d038cdb3f032e5f7a827f77e1ac9188055d07f31a7af28de5a7dc2f365d5405f8f650bc07d94c56cb1fdacb85f1da7c073df3da229e54880664279bb3f3
7
- data.tar.gz: 42c4751cd29a86d81507c1b9932a5e4c7b1b3c455e3fbd09ce7fa6a5398ccd423297092f08473b883abc23a81c735a4029759a241cfaf643e5d6e78b68f2c65e
6
+ metadata.gz: 99eb911e2084e0019876e7f052a6c3dc72674cc6aec718666e541ae23335e0a5e2ede70a3df96934c8ec0bbc6fa88c60a0eccc94c522edbc43e641b3f3732b25
7
+ data.tar.gz: 627d69647e22405d8289b241e3d0b8beb0ebbfaf7d6f7194e9fd2bb2439cb6c074096977bcb673b6831710f951398bb511eb27d101b5a012cc7e1b416419319a
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Release history for google-apis-chat_v1
2
2
 
3
+ ### v0.98.0 (2024-07-25)
4
+
5
+ * Regenerated from discovery document revision 20240709
6
+
7
+ ### v0.97.0 (2024-07-07)
8
+
9
+ * Regenerated from discovery document revision 20240625
10
+
3
11
  ### v0.96.0 (2024-06-23)
4
12
 
5
13
  * Regenerated from discovery document revision 20240613
@@ -22,6 +22,39 @@ module Google
22
22
  module Apis
23
23
  module ChatV1
24
24
 
25
+ # Represents the [access setting](https://support.google.com/chat/answer/
26
+ # 11971020) of the space.
27
+ class AccessSettings
28
+ include Google::Apis::Core::Hashable
29
+
30
+ # Output only. Indicates the access state of the space.
31
+ # Corresponds to the JSON property `accessState`
32
+ # @return [String]
33
+ attr_accessor :access_state
34
+
35
+ # Optional. The resource name of the [target audience](https://support.google.
36
+ # com/a/answer/9934697) who can discover the space, join the space, and preview
37
+ # the messages in the space. If unset, only users or Google Groups who have been
38
+ # individually invited or added to the space can access it. For details, see [
39
+ # Make a space discoverable to a target audience](https://developers.google.com/
40
+ # workspace/chat/space-target-audience). Format: `audiences/`audience`` To use
41
+ # the default target audience for the Google Workspace organization, set to `
42
+ # audiences/default`.
43
+ # Corresponds to the JSON property `audience`
44
+ # @return [String]
45
+ attr_accessor :audience
46
+
47
+ def initialize(**args)
48
+ update!(**args)
49
+ end
50
+
51
+ # Update properties of this object
52
+ def update!(**args)
53
+ @access_state = args[:access_state] if args.key?(:access_state)
54
+ @audience = args[:audience] if args.key?(:audience)
55
+ end
56
+ end
57
+
25
58
  # One or more interactive widgets that appear at the bottom of a message. For
26
59
  # details, see [Add interactive widgets at the bottom of a message](https://
27
60
  # developers.google.com/workspace/chat/create-messages#add-accessory-widgets).
@@ -839,12 +872,11 @@ module Google
839
872
  end
840
873
  end
841
874
 
842
- # A Google Chat app interaction event. To learn about interaction events, see [
843
- # Receive and respond to interactions with your Google Chat app](https://
844
- # developers.google.com/workspace/chat/api/guides/message-formats). To learn
845
- # about event types and for example event payloads, see [Types of Google Chat
846
- # app interaction events](https://developers.google.com/workspace/chat/events).
847
- # In addition to receiving events from user interactions, Chat apps can receive
875
+ # A Google Chat app interaction event that represents and contains data about a
876
+ # user's interaction with a Chat app. To configure your Chat app to receive
877
+ # interaction events, see [Receive and respond to user interactions](https://
878
+ # developers.google.com/workspace/chat/receive-respond-interactions). In
879
+ # addition to receiving events from user interactions, Chat apps can receive
848
880
  # events about changes to spaces, such as when a new member is added to a space.
849
881
  # To learn about space events, see [Work with events from Google Chat](https://
850
882
  # developers.google.com/workspace/chat/events-overview).
@@ -921,8 +953,8 @@ module Google
921
953
  # @return [String]
922
954
  attr_accessor :token
923
955
 
924
- # The type of interaction event. For details, see [Types of Google Chat app
925
- # interaction events](https://developers.google.com/workspace/chat/events).
956
+ # The [type](/workspace/chat/api/reference/rest/v1/EventType) of user
957
+ # interaction with the Chat app, such as `MESSAGE` or `ADDED_TO_SPACE`.
926
958
  # Corresponds to the JSON property `type`
927
959
  # @return [String]
928
960
  attr_accessor :type
@@ -1714,8 +1746,7 @@ module Google
1714
1746
  end
1715
1747
 
1716
1748
  # A column. [Google Workspace Add-ons and Chat apps](https://developers.google.
1717
- # com/workspace/extend): Columns for Google Workspace Add-ons are in Developer
1718
- # Preview.
1749
+ # com/workspace/extend)
1719
1750
  class GoogleAppsCardV1Column
1720
1751
  include Google::Apis::Core::Hashable
1721
1752
 
@@ -3072,8 +3103,7 @@ module Google
3072
3103
  end
3073
3104
 
3074
3105
  # The supported widgets that you can include in a column. [Google Workspace Add-
3075
- # ons and Chat apps](https://developers.google.com/workspace/extend): Columns
3076
- # for Google Workspace Add-ons are in Developer Preview.
3106
+ # ons and Chat apps](https://developers.google.com/workspace/extend)
3077
3107
  class GoogleAppsCardV1Widgets
3078
3108
  include Google::Apis::Core::Hashable
3079
3109
 
@@ -4402,20 +4432,23 @@ module Google
4402
4432
  class SetUpSpaceRequest
4403
4433
  include Google::Apis::Core::Hashable
4404
4434
 
4405
- # Optional. The Google Chat users to invite to join the space. Omit the calling
4406
- # user, as they are added automatically. The set currently allows up to 20
4407
- # memberships (in addition to the caller). For human membership, the `Membership.
4408
- # member` field must contain a `user` with `name` populated (format: `users/`
4409
- # user``) and `type` set to `User.Type.HUMAN`. You can only add human users when
4410
- # setting up a space (adding Chat apps is only supported for direct message
4411
- # setup with the calling app). You can also add members using the user's email
4412
- # as an alias for `user`. For example, the `user.name` can be `users/example@
4413
- # gmail.com`. To invite Gmail users or users from external Google Workspace
4414
- # domains, user's email must be used for ``user``. Optional when setting `Space.
4415
- # spaceType` to `SPACE`. Required when setting `Space.spaceType` to `GROUP_CHAT`,
4416
- # along with at least two memberships. Required when setting `Space.spaceType`
4417
- # to `DIRECT_MESSAGE` with a human user, along with exactly one membership. Must
4418
- # be empty when creating a 1:1 conversation between a human and the calling Chat
4435
+ # Optional. The Google Chat users or groups to invite to join the space. Omit
4436
+ # the calling user, as they are added automatically. The set currently allows up
4437
+ # to 20 memberships (in addition to the caller). For human membership, the `
4438
+ # Membership.member` field must contain a `user` with `name` populated (format: `
4439
+ # users/`user``) and `type` set to `User.Type.HUMAN`. You can only add human
4440
+ # users when setting up a space (adding Chat apps is only supported for direct
4441
+ # message setup with the calling app). You can also add members using the user's
4442
+ # email as an alias for `user`. For example, the `user.name` can be `users/
4443
+ # example@gmail.com`. To invite Gmail users or users from external Google
4444
+ # Workspace domains, user's email must be used for ``user``. For Google group
4445
+ # membership, the `Membership.group_member` field must contain a `group` with `
4446
+ # name` populated (format `groups/`group``). You can only add Google groups when
4447
+ # setting `Space.spaceType` to `SPACE`. Optional when setting `Space.spaceType`
4448
+ # to `SPACE`. Required when setting `Space.spaceType` to `GROUP_CHAT`, along
4449
+ # with at least two memberships. Required when setting `Space.spaceType` to `
4450
+ # DIRECT_MESSAGE` with a human user, along with exactly one membership. Must be
4451
+ # empty when creating a 1:1 conversation between a human and the calling Chat
4419
4452
  # app (when setting `Space.spaceType` to `DIRECT_MESSAGE` and `Space.
4420
4453
  # singleUserBotDm` to `true`).
4421
4454
  # Corresponds to the JSON property `memberships`
@@ -4520,6 +4553,12 @@ module Google
4520
4553
  class Space
4521
4554
  include Google::Apis::Core::Hashable
4522
4555
 
4556
+ # Represents the [access setting](https://support.google.com/chat/answer/
4557
+ # 11971020) of the space.
4558
+ # Corresponds to the JSON property `accessSettings`
4559
+ # @return [Google::Apis::ChatV1::AccessSettings]
4560
+ attr_accessor :access_settings
4561
+
4523
4562
  # Output only. For direct message (DM) spaces with a Chat app, whether the space
4524
4563
  # was created by a Google Workspace administrator. Administrators can install
4525
4564
  # and set up a direct message with a Chat app on behalf of users in their
@@ -4553,13 +4592,8 @@ module Google
4553
4592
  # when creating a space in a Google Workspace organization. Omit this field when
4554
4593
  # creating spaces in the following conditions: * The authenticated user uses a
4555
4594
  # consumer account (unmanaged user account). By default, a space created by a
4556
- # consumer account permits any Google Chat user. * The space is used to [import
4557
- # data to Google Chat] (https://developers.google.com/chat/api/guides/import-
4558
- # data-overview) because import mode spaces must only permit members from the
4559
- # same Google Workspace organization. However, as part of the [Google Workspace
4560
- # Developer Preview Program](https://developers.google.com/workspace/preview),
4561
- # import mode spaces can permit any Google Chat user so this field can then be
4562
- # set for import mode spaces. For existing spaces, this field is output only.
4595
+ # consumer account permits any Google Chat user. For existing spaces, this field
4596
+ # is output only.
4563
4597
  # Corresponds to the JSON property `externalUserAllowed`
4564
4598
  # @return [Boolean]
4565
4599
  attr_accessor :external_user_allowed
@@ -4605,6 +4639,11 @@ module Google
4605
4639
  # @return [String]
4606
4640
  attr_accessor :space_type
4607
4641
 
4642
+ # Output only. The URI for a user to access the space.
4643
+ # Corresponds to the JSON property `spaceUri`
4644
+ # @return [String]
4645
+ attr_accessor :space_uri
4646
+
4608
4647
  # Output only. Deprecated: Use `spaceThreadingState` instead. Whether messages
4609
4648
  # are threaded in this space.
4610
4649
  # Corresponds to the JSON property `threaded`
@@ -4623,6 +4662,7 @@ module Google
4623
4662
 
4624
4663
  # Update properties of this object
4625
4664
  def update!(**args)
4665
+ @access_settings = args[:access_settings] if args.key?(:access_settings)
4626
4666
  @admin_installed = args[:admin_installed] if args.key?(:admin_installed)
4627
4667
  @create_time = args[:create_time] if args.key?(:create_time)
4628
4668
  @display_name = args[:display_name] if args.key?(:display_name)
@@ -4634,6 +4674,7 @@ module Google
4634
4674
  @space_history_state = args[:space_history_state] if args.key?(:space_history_state)
4635
4675
  @space_threading_state = args[:space_threading_state] if args.key?(:space_threading_state)
4636
4676
  @space_type = args[:space_type] if args.key?(:space_type)
4677
+ @space_uri = args[:space_uri] if args.key?(:space_uri)
4637
4678
  @threaded = args[:threaded] if args.key?(:threaded)
4638
4679
  @type = args[:type] if args.key?(:type)
4639
4680
  end
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module ChatV1
18
18
  # Version of the google-apis-chat_v1 gem
19
- GEM_VERSION = "0.96.0"
19
+ GEM_VERSION = "0.98.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.15.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20240613"
25
+ REVISION = "20240709"
26
26
  end
27
27
  end
28
28
  end
@@ -22,6 +22,12 @@ module Google
22
22
  module Apis
23
23
  module ChatV1
24
24
 
25
+ class AccessSettings
26
+ class Representation < Google::Apis::Core::JsonRepresentation; end
27
+
28
+ include Google::Apis::Core::JsonObjectSupport
29
+ end
30
+
25
31
  class AccessoryWidget
26
32
  class Representation < Google::Apis::Core::JsonRepresentation; end
27
33
 
@@ -790,6 +796,14 @@ module Google
790
796
  include Google::Apis::Core::JsonObjectSupport
791
797
  end
792
798
 
799
+ class AccessSettings
800
+ # @private
801
+ class Representation < Google::Apis::Core::JsonRepresentation
802
+ property :access_state, as: 'accessState'
803
+ property :audience, as: 'audience'
804
+ end
805
+ end
806
+
793
807
  class AccessoryWidget
794
808
  # @private
795
809
  class Representation < Google::Apis::Core::JsonRepresentation
@@ -1924,6 +1938,8 @@ module Google
1924
1938
  class Space
1925
1939
  # @private
1926
1940
  class Representation < Google::Apis::Core::JsonRepresentation
1941
+ property :access_settings, as: 'accessSettings', class: Google::Apis::ChatV1::AccessSettings, decorator: Google::Apis::ChatV1::AccessSettings::Representation
1942
+
1927
1943
  property :admin_installed, as: 'adminInstalled'
1928
1944
  property :create_time, as: 'createTime'
1929
1945
  property :display_name, as: 'displayName'
@@ -1936,6 +1952,7 @@ module Google
1936
1952
  property :space_history_state, as: 'spaceHistoryState'
1937
1953
  property :space_threading_state, as: 'spaceThreadingState'
1938
1954
  property :space_type, as: 'spaceType'
1955
+ property :space_uri, as: 'spaceUri'
1939
1956
  property :threaded, as: 'threaded'
1940
1957
  property :type, as: 'type'
1941
1958
  end
@@ -409,39 +409,43 @@ module Google
409
409
  # Resource name of the space. Format: `spaces/`space``
410
410
  # @param [Google::Apis::ChatV1::Space] space_object
411
411
  # @param [String] update_mask
412
- # Required. The updated field paths, comma separated if there are multiple.
413
- # Currently supported field paths: - `display_name` (Only supports changing the
414
- # display name of a space with the `SPACE` type, or when also including the `
415
- # space_type` mask to change a `GROUP_CHAT` space type to `SPACE`. Trying to
416
- # update the display name of a `GROUP_CHAT` or a `DIRECT_MESSAGE` space results
417
- # in an invalid argument error. If you receive the error message `ALREADY_EXISTS`
418
- # when updating the `displayName`, try a different `displayName`. An existing
419
- # space within the Google Workspace organization might already use this display
420
- # name.) - `space_type` (Only supports changing a `GROUP_CHAT` space type to `
421
- # SPACE`. Include `display_name` together with `space_type` in the update mask
422
- # and ensure that the specified space has a non-empty display name and the `
423
- # SPACE` space type. Including the `space_type` mask and the `SPACE` type in the
424
- # specified space when updating the display name is optional if the existing
425
- # space already has the `SPACE` type. Trying to update the space type in other
426
- # ways results in an invalid argument error). `space_type` is not supported with
427
- # admin access. - `space_details` - `space_history_state` (Supports [turning
428
- # history on or off for the space](https://support.google.com/chat/answer/
429
- # 7664687) if [the organization allows users to change their history setting](
430
- # https://support.google.com/a/answer/7664184). Warning: mutually exclusive with
431
- # all other field paths.) `space_history_state` is not supported with admin
432
- # access. - Developer Preview: `access_settings.audience` (Supports changing the
433
- # [access setting](https://support.google.com/chat/answer/11971020) of a space.
434
- # If no audience is specified in the access setting, the space's access setting
435
- # is updated to restricted. Warning: mutually exclusive with all other field
436
- # paths.) `access_settings.audience` is not supported with admin access. -
437
- # Developer Preview: Supports changing the [permission settings](https://support.
438
- # google.com/chat/answer/13340792) of a space, supported field paths include: `
439
- # permission_settings.manage_members_and_groups`, `permission_settings.
440
- # modify_space_details`, `permission_settings.toggle_history`, `
441
- # permission_settings.use_at_mention_all`, `permission_settings.manage_apps`, `
442
- # permission_settings.manage_webhooks`, `permission_settings.reply_messages` (
443
- # Warning: mutually exclusive with all other non-permission settings field paths)
444
- # . `permission_settings` is not supported with admin access.
412
+ # Required. The updated field paths, comma separated if there are multiple. You
413
+ # can update the following fields for a space: - `space_details` - `display_name`
414
+ # : Only supports updating the display name for spaces where `spaceType` field
415
+ # is `SPACE`. If you receive the error message `ALREADY_EXISTS`, try a different
416
+ # value. An existing space within the Google Workspace organization might
417
+ # already use this display name. - `space_type`: Only supports changing a `
418
+ # GROUP_CHAT` space type to `SPACE`. Include `display_name` together with `
419
+ # space_type` in the update mask and ensure that the specified space has a non-
420
+ # empty display name and the `SPACE` space type. Including the `space_type` mask
421
+ # and the `SPACE` type in the specified space when updating the display name is
422
+ # optional if the existing space already has the `SPACE` type. Trying to update
423
+ # the space type in other ways results in an invalid argument error. `space_type`
424
+ # is not supported with admin access. - `space_history_state`: Updates [space
425
+ # history settings](https://support.google.com/chat/answer/7664687) by turning
426
+ # history on or off for the space. Only supported if history settings are
427
+ # enabled for the Google Workspace organization. To update the space history
428
+ # state, you must omit all other field masks in your request. `
429
+ # space_history_state` is not supported with admin access. - `access_settings.
430
+ # audience`: Updates the [access setting](https://support.google.com/chat/answer/
431
+ # 11971020) of who can discover the space, join the space, and preview the
432
+ # messages in named space where `spaceType` field is `SPACE`. If the existing
433
+ # space has a target audience, you can remove the audience and restrict space
434
+ # access by omitting a value for this field mask. To update access settings for
435
+ # a space, the authenticating user must be a space manager and omit all other
436
+ # field masks in your request. You can't update this field if the space is in [
437
+ # import mode](https://developers.google.com/workspace/chat/import-data-overview)
438
+ # . To learn more, see [Make a space discoverable to specific users](https://
439
+ # developers.google.com/workspace/chat/space-target-audience). `access_settings.
440
+ # audience` is not supported with admin access. - Developer Preview: Supports
441
+ # changing the [permission settings](https://support.google.com/chat/answer/
442
+ # 13340792) of a space, supported field paths include: `permission_settings.
443
+ # manage_members_and_groups`, `permission_settings.modify_space_details`, `
444
+ # permission_settings.toggle_history`, `permission_settings.use_at_mention_all`,
445
+ # `permission_settings.manage_apps`, `permission_settings.manage_webhooks`, `
446
+ # permission_settings.reply_messages` (Warning: mutually exclusive with all
447
+ # other non-permission settings field paths). `permission_settings` is not
448
+ # supported with admin access.
445
449
  # @param [String] fields
446
450
  # Selector specifying which fields to include in a partial response.
447
451
  # @param [String] quota_user
@@ -483,24 +487,32 @@ module Google
483
487
  # for the user in the Directory API. For example, if the People API Person
484
488
  # profile ID for `user@example.com` is `123456789`, you can add the user to the
485
489
  # space by setting the `membership.member.name` to `users/user@example.com` or `
486
- # users/123456789`. For a named space or group chat, if the caller blocks, or is
487
- # blocked by some members, or doesn't have permission to add some members, then
488
- # those members aren't added to the created space. To create a direct message (
489
- # DM) between the calling user and another human user, specify exactly one
490
- # membership to represent the human user. If one user blocks the other, the
491
- # request fails and the DM isn't created. To create a DM between the calling
492
- # user and the calling app, set `Space.singleUserBotDm` to `true` and don't
493
- # specify any memberships. You can only use this method to set up a DM with the
494
- # calling app. To add the calling app as a member of a space or an existing DM
495
- # between two human users, see [Invite or add a user or app to a space](https://
496
- # developers.google.com/workspace/chat/create-members). If a DM already exists
497
- # between two users, even when one user blocks the other at the time a request
498
- # is made, then the existing DM is returned. Spaces with threaded replies aren't
499
- # supported. If you receive the error message `ALREADY_EXISTS` when setting up a
500
- # space, try a different `displayName`. An existing space within the Google
501
- # Workspace organization might already use this display name. Requires [user
502
- # authentication](https://developers.google.com/workspace/chat/authenticate-
503
- # authorize-chat-user).
490
+ # users/123456789`. To specify the Google groups to add, add memberships with
491
+ # the appropriate `membership.group_member.name`. To add or invite a Google
492
+ # group, use `groups/`group``, where ``group`` is the `id` for the group from
493
+ # the Cloud Identity Groups API. For example, you can use [Cloud Identity Groups
494
+ # lookup API](https://cloud.google.com/identity/docs/reference/rest/v1/groups/
495
+ # lookup) to retrieve the ID `123456789` for group email `group@example.com`,
496
+ # then you can add the group to the space by setting the `membership.
497
+ # group_member.name` to `groups/123456789`. Group email is not supported, and
498
+ # Google groups can only be added as members in named spaces. For a named space
499
+ # or group chat, if the caller blocks, or is blocked by some members, or doesn't
500
+ # have permission to add some members, then those members aren't added to the
501
+ # created space. To create a direct message (DM) between the calling user and
502
+ # another human user, specify exactly one membership to represent the human user.
503
+ # If one user blocks the other, the request fails and the DM isn't created. To
504
+ # create a DM between the calling user and the calling app, set `Space.
505
+ # singleUserBotDm` to `true` and don't specify any memberships. You can only use
506
+ # this method to set up a DM with the calling app. To add the calling app as a
507
+ # member of a space or an existing DM between two human users, see [Invite or
508
+ # add a user or app to a space](https://developers.google.com/workspace/chat/
509
+ # create-members). If a DM already exists between two users, even when one user
510
+ # blocks the other at the time a request is made, then the existing DM is
511
+ # returned. Spaces with threaded replies aren't supported. If you receive the
512
+ # error message `ALREADY_EXISTS` when setting up a space, try a different `
513
+ # displayName`. An existing space within the Google Workspace organization might
514
+ # already use this display name. Requires [user authentication](https://
515
+ # developers.google.com/workspace/chat/authenticate-authorize-chat-user).
504
516
  # @param [Google::Apis::ChatV1::SetUpSpaceRequest] set_up_space_request_object
505
517
  # @param [String] fields
506
518
  # Selector specifying which fields to include in a partial response.
@@ -539,14 +551,23 @@ module Google
539
551
  # adds the member directly to the specified space. Requires [user authentication]
540
552
  # (https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)
541
553
  # . To specify the member to add, set the `membership.member.name` for the human
542
- # or app member. - To add the calling app to a space or a direct message between
543
- # two human users, use `users/app`. Unable to add other apps to the space. - To
544
- # add a human user, use `users/`user``, where ``user`` can be the email address
545
- # for the user. For users in the same Workspace organization ``user`` can also
546
- # be the `id` for the person from the People API, or the `id` for the user in
547
- # the Directory API. For example, if the People API Person profile ID for `user@
554
+ # or app member, or set the `membership.group_member.name` for the group member.
555
+ # - To add the calling app to a space or a direct message between two human
556
+ # users, use `users/app`. Unable to add other apps to the space. - To add a
557
+ # human user, use `users/`user``, where ``user`` can be the email address for
558
+ # the user. For users in the same Workspace organization ``user`` can also be
559
+ # the `id` for the person from the People API, or the `id` for the user in the
560
+ # Directory API. For example, if the People API Person profile ID for `user@
548
561
  # example.com` is `123456789`, you can add the user to the space by setting the `
549
- # membership.member.name` to `users/user@example.com` or `users/123456789`.
562
+ # membership.member.name` to `users/user@example.com` or `users/123456789`. - To
563
+ # add or invite a Google group in a named space, use `groups/`group``, where ``
564
+ # group`` is the `id` for the group from the Cloud Identity Groups API. For
565
+ # example, you can use [Cloud Identity Groups lookup API](https://cloud.google.
566
+ # com/identity/docs/reference/rest/v1/groups/lookup) to retrieve the ID `
567
+ # 123456789` for group email `group@example.com`, then you can add or invite the
568
+ # group to a named space by setting the `membership.group_member.name` to `
569
+ # groups/123456789`. Group email is not supported, and Google groups can only be
570
+ # added as members in named spaces.
550
571
  # @param [String] parent
551
572
  # Required. The resource name of the space for which to create the membership.
552
573
  # Format: spaces/`space`
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-chat_v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.96.0
4
+ version: 0.98.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-06-23 00:00:00.000000000 Z
11
+ date: 2024-07-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
58
58
  metadata:
59
59
  bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
60
60
  changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.96.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.98.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1
63
63
  post_install_message:
64
64
  rdoc_options: []