You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(knowledge): Drive field mask named a permission field that does not exist
`permittedBy` is not a field of the Permission resource — inheritance lives in
`permissionDetails` — and Drive answers an invalid field selection with 400.
The mask was unconditional, so every `files.list` on this branch failed, in
every access mode, and the suite passed only because every Drive call is mocked
and the assertion checked a prefix of the mask. Caught by a reviewer checking
the mask against the API reference.
Also from that review: `groups.list?domain=` enumerates one domain, while a
Workspace customer routinely owns several — a grant to a group on a secondary
domain named a group the directory never listed, readable by nobody; it is
`customer=my_customer` now. A deleted account's grant no longer mints a token
for whoever is later provisioned with the recycled address. The Admin SDK
calls share the Drive retry wrapper, so one transient error no longer stales a
group. And the `permissionIds` count heuristic is gone: the field counts users
only, so any file with a domain or public grant tripped a needless fallback;
absence of `permissions` is the one signal that matters, and it is kept.
0 commit comments