@@ -1724,34 +1724,7 @@ public Patch setName(java.lang.String name) {
1724
1724
}
1725
1725
1726
1726
/**
1727
- * Required. The updated field paths, comma separated if there are multiple. You can update
1728
- * the following fields for a space: - `space_details` - `display_name`: Only supports
1729
- * updating the display name for spaces where `spaceType` field is `SPACE`. If you receive the
1730
- * error message `ALREADY_EXISTS`, try a different value. An existing space within the Google
1731
- * Workspace organization might already use this display name. - `space_type`: Only supports
1732
- * changing a `GROUP_CHAT` space type to `SPACE`. Include `display_name` together with
1733
- * `space_type` in the update mask and ensure that the specified space has a non-empty display
1734
- * name and the `SPACE` space type. Including the `space_type` mask and the `SPACE` type in
1735
- * the specified space when updating the display name is optional if the existing space
1736
- * already has the `SPACE` type. Trying to update the space type in other ways results in an
1737
- * invalid argument error. `space_type` is not supported with admin access. -
1738
- * `space_history_state`: Updates [space history
1739
- * settings](https://support.google.com/chat/answer/7664687) by turning history on or off for
1740
- * the space. Only supported if history settings are enabled for the Google Workspace
1741
- * organization. To update the space history state, you must omit all other field masks in
1742
- * your request. `space_history_state` is not supported with admin access. -
1743
- * `access_settings.audience`: Updates the [access
1744
- * setting](https://support.google.com/chat/answer/11971020) of who can discover the space,
1745
- * join the space, and preview the messages in named space where `spaceType` field is `SPACE`.
1746
- * If the existing space has a target audience, you can remove the audience and restrict space
1747
- * access by omitting a value for this field mask. To update access settings for a space, the
1748
- * authenticating user must be a space manager and omit all other field masks in your request.
1749
- * You can't update this field if the space is in [import
1750
- * mode](https://developers.google.com/workspace/chat/import-data-overview). To learn more,
1751
- * see [Make a space discoverable to specific
1752
- * users](https://developers.google.com/workspace/chat/space-target-audience).
1753
- * `access_settings.audience` is not supported with admin access. - Developer Preview:
1754
- * Supports changing the [permission
1727
+ * - Supports changing the [permission
1755
1728
* settings](https://support.google.com/chat/answer/13340792) of a space, supported field
1756
1729
* paths include: `permission_settings.manage_members_and_groups`,
1757
1730
* `permission_settings.modify_space_details`, `permission_settings.toggle_history`,
@@ -1763,71 +1736,22 @@ public Patch setName(java.lang.String name) {
1763
1736
@ com .google .api .client .util .Key
1764
1737
private String updateMask ;
1765
1738
1766
- /** Required. The updated field paths, comma separated if there are multiple. You can update the
1767
- following fields for a space: - `space_details` - `display_name`: Only supports updating the
1768
- display name for spaces where `spaceType` field is `SPACE`. If you receive the error message
1769
- `ALREADY_EXISTS`, try a different value. An existing space within the Google Workspace organization
1770
- might already use this display name. - `space_type`: Only supports changing a `GROUP_CHAT` space
1771
- type to `SPACE`. Include `display_name` together with `space_type` in the update mask and ensure
1772
- that the specified space has a non-empty display name and the `SPACE` space type. Including the
1773
- `space_type` mask and the `SPACE` type in the specified space when updating the display name is
1774
- optional if the existing space already has the `SPACE` type. Trying to update the space type in
1775
- other ways results in an invalid argument error. `space_type` is not supported with admin access. -
1776
- `space_history_state`: Updates [space history
1777
- settings](https://support.google.com/chat/answer/7664687) by turning history on or off for the
1778
- space. Only supported if history settings are enabled for the Google Workspace organization. To
1779
- update the space history state, you must omit all other field masks in your request.
1780
- `space_history_state` is not supported with admin access. - `access_settings.audience`: Updates the
1781
- [access setting](https://support.google.com/chat/answer/11971020) of who can discover the space,
1782
- join the space, and preview the messages in named space where `spaceType` field is `SPACE`. If the
1783
- existing space has a target audience, you can remove the audience and restrict space access by
1784
- omitting a value for this field mask. To update access settings for a space, the authenticating
1785
- user must be a space manager and omit all other field masks in your request. You can't update this
1786
- field if the space is in [import mode](https://developers.google.com/workspace/chat/import-data-
1787
- overview). To learn more, see [Make a space discoverable to specific
1788
- users](https://developers.google.com/workspace/chat/space-target-audience).
1789
- `access_settings.audience` is not supported with admin access. - Developer Preview: Supports
1790
- changing the [permission settings](https://support.google.com/chat/answer/13340792) of a space,
1791
- supported field paths include: `permission_settings.manage_members_and_groups`,
1792
- `permission_settings.modify_space_details`, `permission_settings.toggle_history`,
1793
- `permission_settings.use_at_mention_all`, `permission_settings.manage_apps`,
1794
- `permission_settings.manage_webhooks`, `permission_settings.reply_messages` (Warning: mutually
1795
- exclusive with all other non-permission settings field paths). `permission_settings` is not
1796
- supported with admin access.
1739
+ /**- Supports changing the [permission settings](https://support.google.com/chat/answer/13340792) of a
1740
+ - space, supported field paths include: `permission_settings.manage_members_and_groups`,
1741
+ - `permission_settings.modify_space_details`, `permission_settings.toggle_history`,
1742
+ - `permission_settings.use_at_mention_all`, `permission_settings.manage_apps`,
1743
+ - `permission_settings.manage_webhooks`, `permission_settings.reply_messages` (Warning: mutually
1744
+ - exclusive with all other non-permission settings field paths). `permission_settings` is not
1745
+ - supported with admin access.
1746
+ -
1747
+
1797
1748
*/
1798
1749
public String getUpdateMask () {
1799
1750
return updateMask ;
1800
1751
}
1801
1752
1802
1753
/**
1803
- * Required. The updated field paths, comma separated if there are multiple. You can update
1804
- * the following fields for a space: - `space_details` - `display_name`: Only supports
1805
- * updating the display name for spaces where `spaceType` field is `SPACE`. If you receive the
1806
- * error message `ALREADY_EXISTS`, try a different value. An existing space within the Google
1807
- * Workspace organization might already use this display name. - `space_type`: Only supports
1808
- * changing a `GROUP_CHAT` space type to `SPACE`. Include `display_name` together with
1809
- * `space_type` in the update mask and ensure that the specified space has a non-empty display
1810
- * name and the `SPACE` space type. Including the `space_type` mask and the `SPACE` type in
1811
- * the specified space when updating the display name is optional if the existing space
1812
- * already has the `SPACE` type. Trying to update the space type in other ways results in an
1813
- * invalid argument error. `space_type` is not supported with admin access. -
1814
- * `space_history_state`: Updates [space history
1815
- * settings](https://support.google.com/chat/answer/7664687) by turning history on or off for
1816
- * the space. Only supported if history settings are enabled for the Google Workspace
1817
- * organization. To update the space history state, you must omit all other field masks in
1818
- * your request. `space_history_state` is not supported with admin access. -
1819
- * `access_settings.audience`: Updates the [access
1820
- * setting](https://support.google.com/chat/answer/11971020) of who can discover the space,
1821
- * join the space, and preview the messages in named space where `spaceType` field is `SPACE`.
1822
- * If the existing space has a target audience, you can remove the audience and restrict space
1823
- * access by omitting a value for this field mask. To update access settings for a space, the
1824
- * authenticating user must be a space manager and omit all other field masks in your request.
1825
- * You can't update this field if the space is in [import
1826
- * mode](https://developers.google.com/workspace/chat/import-data-overview). To learn more,
1827
- * see [Make a space discoverable to specific
1828
- * users](https://developers.google.com/workspace/chat/space-target-audience).
1829
- * `access_settings.audience` is not supported with admin access. - Developer Preview:
1830
- * Supports changing the [permission
1754
+ * - Supports changing the [permission
1831
1755
* settings](https://support.google.com/chat/answer/13340792) of a space, supported field
1832
1756
* paths include: `permission_settings.manage_members_and_groups`,
1833
1757
* `permission_settings.modify_space_details`, `permission_settings.toggle_history`,
0 commit comments