Reference G: Unified Asset Inventory fields and deep links
This appendix documents the two Code-to-Cloud fields recorded on every code-side and cloud-side asset in the Unified Asset Inventory (UAI), used both by the dashboard's Traced/Untraced counts and as filters within the UAI tables.
Code-2-Cloud
Forward
CODE, BUILD, DEPLOY, RUNTIME
The furthest forward stage the asset's lineage reaches. CODE means no forward trace was established; RUNTIME means the lineage reaches a runtime workload.
Cloud-2-Code
Backward
CODE, BUILD, DEPLOY, RUNTIME
The furthest backward stage the asset's lineage reaches. CODE means the lineage reaches a repository; RUNTIME means no backward trace was established.
Examples
Onboarded VCS Repository
Code-2-Cloud
CODE
The repository could not be traced to any pipeline, registry, or runtime asset.
CI/CD Pipeline
Code-2-Cloud
RUNTIME
The pipeline's lineage reaches a runtime workload.
Runtime Container Image
Cloud-2-Code
BUILD
The runtime image was traced back to a CI/CD pipeline but not to a repository.
IaC Resource
Code-2-Cloud
RUNTIME
The IaC resource has a YOR tag and matches a deployed cloud asset.
Note: A
NULLvalue for either field indicates that lineage has not yet been calculated for the asset (for example, the asset was recently onboarded). The dashboard treatsNULLas untraced for the per-stage map.
Cross-page deep links
Every map element in the Coverage dashboard links to the corresponding UAI page with the C-2-C field filter pre-applied, and inherits the dashboard's active page-level filters (Application, Provider, Organization). For example, in the Code-2-Cloud Artifact view, selecting the Code-stage untraced area links to the VCS Repository page filtered to Code-2-Cloud = CODE; selecting the Runtime-stage traced area links to the same page filtered to Code-2-Cloud = RUNTIME. The per-provider tooltip on each color area appends a provider = <hovered provider> filter to the link target.
Last updated
Was this helpful?
