The name of the source asset node.

The name of the target asset node.

An edge from a Data asset to an asset configured by the Data payload's proto message type.

This edge type is used to provide a suggested configuration for the target asset.

A map from node names to asset nodes.

Node names are used to define edges and can be used for other purposes, such as to auto-generate asset instance names in a solution.

May not entail cycles.

The ID of the asset assigned to this node. The asset itself is defined elsewhere. E.g., if this graph is part of a HardwareDeviceManifest, then this value corresponds to the key of the asset in the HardwareDeviceManifest.assets map.

The description of the installed assets, in the order requested for installation.

The fully qualified proto name of the data payload.

Deprecated: use asset_types instead.

Filter assets by type (OR).

Filter by assets that provide all of the specified interfaces (exact match).

The nature of the interface depends on the asset type, but is always represented as a string. For example, a Data asset provides a proto of a specific type, and its "interface" is the fully qualified name of that proto. A Service can provide a gRPC service, and its "interface" is the fully qualified proto prefix of that gRPC service.

Filter assets by asset tag.

The list of gRPC services that the HardwareDevice exposes.

Order by which to sort the assets.

If true, sort assets in descending order.

Pass this token to the subsequent list request to obtain the next page.

The list of gRPC services that the Service exposes.

Use a default policy, which may change with platform updates.

Reject a request to delete an asset that is currently in use.

Unspecified. Defaults to ORDER_BY_DISPLAY_NAME.

Use a default policy, which may change with platform updates.

Reject a request to delete an asset that is currently in use.

Use a default policy, which may change with platform updates.

Only add new assets to the solution and reject any that would trigger an update of any installed asset.

Only update assets if they are currently unused.

Only update assets if all are considered reasonably compatible. This may allow backwards incompatible changes if it will not cause problems for the solution. If an asset is unused, then any update will be allow.