An asset feed used to export asset updates to a destinations. An asset feed filter controls what updates are exported. The asset feed must be created within a project, organization, or folder. Supported destinations are: Pub/Sub topics.
Required. The format will be projects/{projectNumber}/feeds/{client-assigned_feed_identifier} or folders/{folder_number}/feeds/{client-assigned_feed_identifier} or organizations/{organization_number}/feeds/{client-assigned_feed_identifier}
The client-assigned feed identifier must be unique within the parent project/folder/organization.
assetNames[]
string
A list of the full names of the assets to receive updates. You must specify either or both of assetNames and assetTypes. Only asset updates matching specified assetNames or assetTypes are exported to the feed. Example: //compute.googleapis.com/projects/my_project_123/zones/zone1/instances/instance1. For a list of the full names for supported asset types, see Resource name format.
assetTypes[]
string
A list of types of the assets to receive updates. You must specify either or both of assetNames and assetTypes. Only asset updates matching specified assetNames or assetTypes are exported to the feed. Example: "compute.googleapis.com/Disk"
A condition which determines whether an asset update should be published. If specified, an asset will be returned only when the expression evaluates to true. When set, expression field in the Expr must be a valid CEL expression on a TemporalAsset with name temporal_asset. Example: a Feed with expression ("temporal_asset.deleted == true") will only publish Asset deletions. Other fields of Expr are optional.
A list of relationship types to output, for example: INSTANCE_TO_INSTANCEGROUP. This field should only be specified if contentType=RELATIONSHIP. * If specified: it outputs specified relationship updates on the [assetNames] or the [assetTypes]. It returns an error if any of the [relationshipTypes] doesn't belong to the supported relationship types of the [assetNames] or [assetTypes], or any of the [assetNames] or the [assetTypes] doesn't belong to the source types of the [relationshipTypes]. * Otherwise: it outputs the supported relationships of the types of [assetNames] and [assetTypes] or returns an error if any of the [assetNames] or the [assetTypes] has no replationship support. See Introduction to Cloud Asset Inventory for all supported asset types and relationship types.
ContentType
Asset content type.
Enums
CONTENT_TYPE_UNSPECIFIED
Unspecified content type.
RESOURCE
Resource metadata.
IAM_POLICY
The actual IAM policy set on a resource.
ORG_POLICY
The organization policy set on an asset.
ACCESS_POLICY
The Access Context Manager policy set on an asset.
OS_INVENTORY
The runtime OS Inventory information.
RELATIONSHIP
The related resources.
FeedOutputConfig
Output configuration for asset feed destination.
JSON representation
{// Union field destination can be only one of the following:"pubsubDestination": {object (PubsubDestination)}// End of list of possible types for union field destination.}
Fields
Union field destination. Asset feed destination. destination can be only one of the following:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-08 UTC."],[[["\u003cp\u003eAsset feeds export asset updates to specified destinations, such as Pub/Sub topics, and can be filtered by asset names or types.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003econtentType\u003c/code\u003e field determines the type of asset content included in the updates, ranging from resource metadata to IAM policies and relationships.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003efeedOutputConfig\u003c/code\u003e defines the destination where updates are published, and currently only supports Pub/Sub destinations through the \u003ccode\u003epubsubDestination\u003c/code\u003e field.\u003c/p\u003e\n"],["\u003cp\u003eEach feed can specify conditions using CEL expressions to control which asset updates are published, allowing for filtering based on properties like whether an asset was deleted.\u003c/p\u003e\n"],["\u003cp\u003eAvailable methods for managing asset feeds include \u003ccode\u003ecreate\u003c/code\u003e, \u003ccode\u003edelete\u003c/code\u003e, \u003ccode\u003eget\u003c/code\u003e, \u003ccode\u003elist\u003c/code\u003e, and \u003ccode\u003epatch\u003c/code\u003e, providing comprehensive control over feed configuration and lifecycle.\u003c/p\u003e\n"]]],[],null,["# REST Resource: feeds\n\n- [Resource: Feed](#Feed)\n - [JSON representation](#Feed.SCHEMA_REPRESENTATION)\n- [ContentType](#ContentType)\n- [FeedOutputConfig](#FeedOutputConfig)\n - [JSON representation](#FeedOutputConfig.SCHEMA_REPRESENTATION)\n- [PubsubDestination](#PubsubDestination)\n - [JSON representation](#PubsubDestination.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: Feed\n--------------\n\nAn asset feed used to export asset updates to a destinations. An asset feed filter controls what updates are exported. The asset feed must be created within a project, organization, or folder. Supported destinations are: Pub/Sub topics.\n\nContentType\n-----------\n\nAsset content type.\n\nFeedOutputConfig\n----------------\n\nOutput configuration for asset feed destination.\n\nPubsubDestination\n-----------------\n\nA Pub/Sub destination."]]