Fixed
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
pi...@google.com <pi...@google.com>
jp...@google.com <jp...@google.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
Description
Description
The published discovery documenthttps://groupssettings.googleapis.com/$discovery/rest?version=v1 for the groupssettings v1 API has the following description for the whoCanJoin field of the Groups resource:
Permission to join group. Possible values are:
Note that the descriptions for
ANYONE_CAN_JOIN
andALL_IN_DOMAIN_CAN_JOIN
are swapped.The reference documentation on developers.google.com ( link ) is correct, suggesting that the published discovery document just needs to be updated.
Impact
This is causing confusion for customers using client libraries. e.g.https://github.com/googleapis/google-api-ruby-client/issues/19535