Repository navigation
Compute's aggregate lists do not support resource's field selection #711
Description
Activity
There are no plans to implement this on the service side (there seem to be no user interest). Will reopen in case some user requires this feature.
added 6 commits that reference this issue on Jun 23, 2022
added a commit that references this issue on Jul 18, 2022
added a commit that references this issue on Jul 27, 2022
added 3 commits that reference this issue on Aug 9, 2022
16 remaining items
added 2 commits that reference this issue on Feb 1, 2023
added a commit that references this issue on Dec 22, 2025
added a commit that references this issue on Jan 6, 2026
added 2 commits that reference this issue on Jan 22, 2026
added a commit that references this issue on Feb 24, 2026
added a commit that references this issue on Mar 11, 2026
added a commit that references this issue on Mar 12, 2026
added a commit that references this issue on Mar 23, 2026
added a commit that references this issue on Mar 30, 2026
added a commit that references this issue on Apr 1, 2026
added a commit that references this issue on Jul 13, 2026
Aggregate lists'
fieldsoption only allows to select the following fields:Shouldn't selecting fields of the listed resources be supported as well?
It would be nice to be able to write a
fieldoption like:items(selfLink),nextPageTokenthat only returns the next page token and the selfLink field for each resource.