Interested in Google Cloud’s List Assets API?
Noelle Easterday
Are you a Cloud Asset Inventory Export API user? If you
use the Export API to export cloud asset metadata but don’t need the GCS storage or BigQuery part, or
you are interested in the Export API but don’t want to deal with files or BigQuery
then Cloud Asset Inventory List API might be what you are looking for! List API returns the assets metadata results in responses with pagination support and is approaching beta launch.
We believe the List API addresses many of the challenges raised with ExportAssets. With beta release approaching, we’d appreciate your feedback on List API, so any remaining gaps can be identified and addressed prior to launch.
More details about the List API are included below. Please contact us at gcp-asset-inventory...@googlegroups.com with any additional information or asks for support so that we may help you try out the new API.
Thank you,
Google Cloud Asset Inventory team
ListAssets Benefits vs ExportAssets
Because results are returned directly in the API response
No supplemental storage or services are needed: no GCS buckets, no BigQuery datasets.
No additional transformations are needed to extract results from storage.
No additional operations are needed, eg. to check on the status of an export
Usage Details
Signature. The API signature is very similar to Export API, and sample code is available for the basic scenario in Python, Java, Node.js, and Go.
Functionality. Currently the API supports:
Listing by a project/organization/folder.
Listing RESOURCE/IAM_POLICY as the contentType.
Limitations. As an API supporting pagination, there’s a page size limit for each API response, 1000 at maximum and 100 as the current default
Permissions
cloudasset.assets.listResource permission for listing RESOURCE
cloudasset.assets.listIamPolicy for listing IAM_POLICY.
Note: Both roles/cloudasset.viewer and roles/cloudasset.owner have the required permissions.
Feedback
Share your feedback at: gcp-asset-inventory...@googlegroups.com.
