google-apis-chat_v1 0.66.0 → 0.68.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -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.66.0"
19
+ GEM_VERSION = "0.68.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.12.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20230718"
25
+ REVISION = "20230806"
26
26
  end
27
27
  end
28
28
  end
@@ -1522,6 +1522,7 @@ module Google
1522
1522
  class Representation < Google::Apis::Core::JsonRepresentation
1523
1523
  property :admin_installed, as: 'adminInstalled'
1524
1524
  property :display_name, as: 'displayName'
1525
+ property :external_user_allowed, as: 'externalUserAllowed'
1525
1526
  property :name, as: 'name'
1526
1527
  property :single_user_bot_dm, as: 'singleUserBotDm'
1527
1528
  property :space_details, as: 'spaceDetails', class: Google::Apis::ChatV1::SpaceDetails, decorator: Google::Apis::ChatV1::SpaceDetails::Representation
@@ -139,11 +139,13 @@ module Google
139
139
  execute_or_queue_command(command, &block)
140
140
  end
141
141
 
142
- # Creates a named space. Spaces grouped by topics or that have guest access aren'
143
- # t supported. For an example, see [Create a space](https://developers.google.
144
- # com/chat/api/guides/v1/spaces/create). Requires [user authentication](https://
145
- # developers.google.com/chat/api/guides/auth/users) and the `chat.spaces.create`
146
- # or `chat.spaces` scope.
142
+ # Creates a named space. Spaces grouped by topics aren't supported. For an
143
+ # example, see [Create a space](https://developers.google.com/chat/api/guides/v1/
144
+ # spaces/create). If you receive the error message `ALREADY_EXISTS` when
145
+ # creating a space, try a different `displayName`. An existing space within the
146
+ # Google Workspace organization might already use this display name. Requires [
147
+ # user authentication](https://developers.google.com/chat/api/guides/auth/users)
148
+ # and the `chat.spaces.create` or `chat.spaces` scope.
147
149
  # @param [Google::Apis::ChatV1::Space] space_object
148
150
  # @param [String] request_id
149
151
  # Optional. A unique identifier for this request. A random UUID is recommended.
@@ -232,7 +234,10 @@ module Google
232
234
  # or the `id` for the [user](https://developers.google.com/admin-sdk/directory/
233
235
  # reference/rest/v1/users) in the Directory API. For example, if the People API `
234
236
  # Person.resourceName` is `people/123456789`, you can find a direct message with
235
- # that person by using `users/123456789` as the `name`.
237
+ # that person by using `users/123456789` as the `name`. When [authenticated as a
238
+ # user](https://developers.google.com/chat/api/guides/auth/users), you can use
239
+ # the email as an alias for ``user``. For example, `users/example@gmail.com`
240
+ # where `example@gmail.com` is the email of the Google Chat user.
236
241
  # @param [String] fields
237
242
  # Selector specifying which fields to include in a partial response.
238
243
  # @param [String] quota_user
@@ -362,9 +367,12 @@ module Google
362
367
  end
363
368
 
364
369
  # Updates a space. For an example, see [Update a space](https://developers.
365
- # google.com/chat/api/guides/v1/spaces/update). Requires [user authentication](
366
- # https://developers.google.com/chat/api/guides/auth/users) and the `chat.spaces`
367
- # scope.
370
+ # google.com/chat/api/guides/v1/spaces/update). If you're updating the `
371
+ # displayName` field and receive the error message `ALREADY_EXISTS`, try a
372
+ # different display name.. An existing space within the Google Workspace
373
+ # organization might already use this display name. Requires [user
374
+ # authentication](https://developers.google.com/chat/api/guides/auth/users) and
375
+ # the `chat.spaces` scope.
368
376
  # @param [String] name
369
377
  # Resource name of the space. Format: `spaces/`space``
370
378
  # @param [Google::Apis::ChatV1::Space] space_object
@@ -374,18 +382,20 @@ module Google
374
382
  # display name of a space with the `SPACE` type, or when also including the `
375
383
  # space_type` mask to change a `GROUP_CHAT` space type to `SPACE`. Trying to
376
384
  # update the display name of a `GROUP_CHAT` or a `DIRECT_MESSAGE` space results
377
- # in an invalid argument error.) - `space_type` (Only supports changing a `
378
- # GROUP_CHAT` space type to `SPACE`. Include `display_name` together with `
379
- # space_type` in the update mask and ensure that the specified space has a non-
380
- # empty display name and the `SPACE` space type. Including the `space_type` mask
381
- # and the `SPACE` type in the specified space when updating the display name is
382
- # optional if the existing space already has the `SPACE` type. Trying to update
383
- # the space type in other ways results in an invalid argument error). - `
384
- # space_details` - `space_history_state` (Supports [turning history on or off
385
- # for the space](https://support.google.com/chat/answer/7664687) if [the
386
- # organization allows users to change their history setting](https://support.
387
- # google.com/a/answer/7664184). Warning: mutually exclusive with all other field
388
- # paths.)
385
+ # in an invalid argument error. If you receive the error message `ALREADY_EXISTS`
386
+ # when updating the `displayName`, try a different `displayName`. An existing
387
+ # space within the Google Workspace organization might already use this display
388
+ # name.) - `space_type` (Only supports changing a `GROUP_CHAT` space type to `
389
+ # SPACE`. Include `display_name` together with `space_type` in the update mask
390
+ # and ensure that the specified space has a non-empty display name and the `
391
+ # SPACE` space type. Including the `space_type` mask and the `SPACE` type in the
392
+ # specified space when updating the display name is optional if the existing
393
+ # space already has the `SPACE` type. Trying to update the space type in other
394
+ # ways results in an invalid argument error). - `space_details` - `
395
+ # space_history_state` (Supports [turning history on or off for the space](https:
396
+ # //support.google.com/chat/answer/7664687) if [the organization allows users to
397
+ # change their history setting](https://support.google.com/a/answer/7664184).
398
+ # Warning: mutually exclusive with all other field paths.)
389
399
  # @param [String] fields
390
400
  # Selector specifying which fields to include in a partial response.
391
401
  # @param [String] quota_user
@@ -421,27 +431,30 @@ module Google
421
431
  # in the request. For an example, see [Set up a space](https://developers.google.
422
432
  # com/chat/api/guides/v1/spaces/set-up). To specify the human members to add,
423
433
  # add memberships with the appropriate `member.name` in the `SetUpSpaceRequest`.
424
- # To add a human user, use `users/`user``, where ``user`` is either the ``
425
- # person_id`` for the [person](https://developers.google.com/people/api/rest/v1/
426
- # people) from the People API, or the `id` for the [user](https://developers.
427
- # google.com/admin-sdk/directory/reference/rest/v1/users) in the Admin SDK
428
- # Directory API. For example, if the People API `Person` `resourceName` is `
429
- # people/123456789`, you can add the user to the space by including a membership
430
- # with `users/123456789` as the `member.name`. For a space or group chat, if the
431
- # caller blocks or is blocked by some members, then those members aren't added
432
- # to the created space. To create a direct message (DM) between the calling user
433
- # and another human user, specify exactly one membership to represent the human
434
- # user. If one user blocks the other, the request fails and the DM isn't created.
435
- # To create a DM between the calling user and the calling app, set `Space.
434
+ # To add a human user, use `users/`user``, where ``user`` can be the email
435
+ # address for the user. For users in the same Workspace organization ``user``
436
+ # can also be the ``person_id`` for the person from the People API, or the `id`
437
+ # for the user in the Directory API. For example, if the People API Person `
438
+ # resourceName` for `user@example.com` is `people/123456789`, you can add the
439
+ # user to the space by setting the `membership.member.name` to `users/user@
440
+ # example.com` or `users/123456789`. For a space or group chat, if the caller
441
+ # blocks or is blocked by some members, then those members aren't added to the
442
+ # created space. To create a direct message (DM) between the calling user and
443
+ # another human user, specify exactly one membership to represent the human user.
444
+ # If one user blocks the other, the request fails and the DM isn't created. To
445
+ # create a DM between the calling user and the calling app, set `Space.
436
446
  # singleUserBotDm` to `true` and don't specify any memberships. You can only use
437
447
  # this method to set up a DM with the calling app. To add the calling app as a
438
448
  # member of a space or an existing DM between two human users, see [create a
439
449
  # membership](https://developers.google.com/chat/api/guides/v1/members/create).
440
450
  # If a DM already exists between two users, even when one user blocks the other
441
451
  # at the time a request is made, then the existing DM is returned. Spaces with
442
- # threaded replies or guest access aren't supported. Requires [user
443
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
444
- # the `chat.spaces.create` or `chat.spaces` scope.
452
+ # threaded replies aren't supported. If you receive the error message `
453
+ # ALREADY_EXISTS` when setting up a space, try a different `displayName`. An
454
+ # existing space within the Google Workspace organization might already use this
455
+ # display name. Requires [user authentication](https://developers.google.com/
456
+ # chat/api/guides/auth/users) and the `chat.spaces.create` or `chat.spaces`
457
+ # scope.
445
458
  # @param [Google::Apis::ChatV1::SetUpSpaceRequest] set_up_space_request_object
446
459
  # @param [String] fields
447
460
  # Selector specifying which fields to include in a partial response.
@@ -483,13 +496,13 @@ module Google
483
496
  # the member to add, set the `membership.member.name` in the `
484
497
  # CreateMembershipRequest`: - To add the calling app to a space or a direct
485
498
  # message between two human users, use `users/app`. Unable to add other apps to
486
- # the space. - To add a human user, use `users/`user``, where ``user`` is either
487
- # the ``person_id`` for the [person](https://developers.google.com/people/api/
488
- # rest/v1/people) from the People API, or the `id` for the [user](https://
489
- # developers.google.com/admin-sdk/directory/reference/rest/v1/users) in the
490
- # Directory API. For example, if the People API `Person` `resourceName` is `
491
- # people/123456789`, you can add the user to the space by setting the `
492
- # membership.member.name` to `users/123456789`.
499
+ # the space. - To add a human user, use `users/`user``, where ``user`` can be
500
+ # the email address for the user. For users in the same Workspace organization ``
501
+ # user`` can also be the ``person_id`` for the person from the People API, or
502
+ # the `id` for the user in the Directory API. For example, if the People API
503
+ # Person `resourceName` for `user@example.com` is `people/123456789`, you can
504
+ # add the user to the space by setting the `membership.member.name` to `users/
505
+ # user@example.com` or `users/123456789`.
493
506
  # @param [String] parent
494
507
  # Required. The resource name of the space for which to create the membership.
495
508
  # Format: spaces/`space`
@@ -531,10 +544,12 @@ module Google
531
544
  # Required. Resource name of the membership to delete. Chat apps can delete
532
545
  # human users' or their own memberships. Chat apps can't delete other apps'
533
546
  # memberships. When deleting a human membership, requires the `chat.memberships`
534
- # scope and `spaces/`space`/members/`member`` format. When deleting an app
535
- # membership, requires the `chat.memberships.app` scope and `spaces/`space`/
536
- # members/app` format. Format: `spaces/`space`/members/`member`` or `spaces/`
537
- # space`/members/app`
547
+ # scope and `spaces/`space`/members/`member`` format. You can use the email as
548
+ # an alias for ``member``. For example, `spaces/`space`/members/example@gmail.
549
+ # com` where `example@gmail.com` is the email of the Google Chat user. When
550
+ # deleting an app membership, requires the `chat.memberships.app` scope and `
551
+ # spaces/`space`/members/app` format. Format: `spaces/`space`/members/`member``
552
+ # or `spaces/`space`/members/app`.
538
553
  # @param [String] fields
539
554
  # Selector specifying which fields to include in a partial response.
540
555
  # @param [String] quota_user
@@ -573,7 +588,11 @@ module Google
573
588
  # @param [String] name
574
589
  # Required. Resource name of the membership to retrieve. To get the app's own
575
590
  # membership, you can optionally use `spaces/`space`/members/app`. Format: `
576
- # spaces/`space`/members/`member`` or `spaces/`space`/members/app`
591
+ # spaces/`space`/members/`member`` or `spaces/`space`/members/app` When [
592
+ # authenticated as a user](https://developers.google.com/chat/api/guides/auth/
593
+ # users), you can use the user's email as an alias for ``member``. For example, `
594
+ # spaces/`space`/members/example@gmail.com` where `example@gmail.com` is the
595
+ # email of the Google Chat user.
577
596
  # @param [String] fields
578
597
  # Selector specifying which fields to include in a partial response.
579
598
  # @param [String] quota_user
@@ -716,11 +735,11 @@ module Google
716
735
  # Optional. A unique request ID for this message. Specifying an existing request
717
736
  # ID returns the message created with that ID instead of creating a new message.
718
737
  # @param [String] thread_key
719
- # Optional. Deprecated: Use thread.thread_key instead. Opaque thread identifier.
720
- # To start or add to a thread, create a message and specify a `threadKey` or the
721
- # thread.name. For example usage, see [Start or reply to a message thread](https:
722
- # //developers.google.com/chat/api/guides/crudl/messages#
723
- # start_or_reply_to_a_message_thread).
738
+ # Optional. Deprecated: Use thread.thread_key instead. ID for the thread.
739
+ # Supports up to 4000 characters. To start or add to a thread, create a message
740
+ # and specify a `threadKey` or the thread.name. For example usage, see [Start or
741
+ # reply to a message thread](https://developers.google.com/chat/api/guides/crudl/
742
+ # messages#start_or_reply_to_a_message_thread).
724
743
  # @param [String] fields
725
744
  # Selector specifying which fields to include in a partial response.
726
745
  # @param [String] quota_user
@@ -761,6 +780,8 @@ module Google
761
780
  # service-accounts) and [user authentication](https://developers.google.com/chat/
762
781
  # api/guides/auth/users). [User authentication](https://developers.google.com/
763
782
  # chat/api/guides/auth/users) requires the `chat.messages` authorization scope.
783
+ # Requests authenticated with service accounts can only delete messages created
784
+ # by the calling Chat app.
764
785
  # @param [String] name
765
786
  # Required. Resource name of the message that you want to delete, in the form `
766
787
  # spaces/*/messages/*` Example: `spaces/AAAAAAAAAAA/messages/BBBBBBBBBBB.
@@ -846,8 +867,7 @@ module Google
846
867
  # from blocked members and spaces. For an example, see [List messages](/chat/api/
847
868
  # guides/v1/messages/list). Requires [user authentication](https://developers.
848
869
  # google.com/chat/api/guides/auth/users) and the `chat.messages` or `chat.
849
- # messages.readonly` authorization scope. This method is only supported in
850
- # spaces that don't allow users from outside the Workspace organization to join.
870
+ # messages.readonly` authorization scope.
851
871
  # @param [String] parent
852
872
  # Required. The resource name of the space to list messages from. Format: `
853
873
  # spaces/`space``
@@ -929,7 +949,8 @@ module Google
929
949
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
930
950
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
931
951
  # User authentication](https://developers.google.com/chat/api/guides/auth/users)
932
- # requires the `chat.messages` authorization scope.
952
+ # requires the `chat.messages` authorization scope. Requests authenticated with
953
+ # service accounts can only update messages created by the calling Chat app.
933
954
  # @param [String] name
934
955
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
935
956
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
@@ -985,7 +1006,8 @@ module Google
985
1006
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
986
1007
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
987
1008
  # User authentication](https://developers.google.com/chat/api/guides/auth/users)
988
- # requires the `chat.messages` authorization scope.
1009
+ # requires the `chat.messages` authorization scope. Requests authenticated with
1010
+ # service accounts can only update messages created by the calling Chat app.
989
1011
  # @param [String] name
990
1012
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
991
1013
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
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.66.0
4
+ version: 0.68.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: 2023-07-23 00:00:00.000000000 Z
11
+ date: 2023-08-13 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.66.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.68.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: []