For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex Cloud Runtime

Reference D: Recommended actions by view and stage

This appendix lists the recommended-action catalog surfaced by the Coverage dashboard's Insights region, by view and stage.

Code-2-Cloud artifact

Stage
Insight title
Action label
Action button

Code → Build

VCS Repositories without traces to build

Onboarding suggested

Onboard CI/CD instances → Data Sources

Build → Deploy

VCS Repositories without traces to deploy

Onboarding suggested

Onboard Container Registries → Data Sources

Deploy → Runtime

VCS Repositories reaching Deploy and not Runtime

Onboarding suggested

Onboard Cloud Accounts → Data Sources

Code-2-Cloud infrastructure

Stage
Insight title
Action label
Action button

Code → Runtime

IaC resources without YOR tag cannot be traced to runtime

Tagging Needed

No one-click action — apply YOR via the tagging bot

Code → Runtime

IaC resources with YOR tag not traced to runtime

Onboarding suggested

Onboard Cloud Accounts → Data Sources

Code → Runtime

Cloud assets without YOR tag can be tagged manually

Tagging Needed

No one-click action — apply YOR manually or via the tagging bot

Cloud-2-Code artifact

Stage
Insight title
Action label
Action button

Runtime → Deploy

Runtime Container Images not traced to Deploy

Onboarding suggested

Onboard Container Registries

Deploy → Build

Runtime Container Images not traced from Deploy to Build

Onboarding suggested

Onboard CI/CD instances

Runtime → Build

Runtime VM Instances not traced to Build

Onboarding suggested

Onboard CI/CD instances

Build → Code

Runtime Images/VM Instances traced to pipelines but not to repos

Onboarding suggested

Onboard VCS Organization/repo

Cloud-2-Code infrastructure

Stage
Insight title
Action label
Action button

Runtime → Code

Cloud assets without YOR tag cannot be traced to their IaC resource

Tagging Needed

No one-click action — apply YOR manually or via the tagging bot

Note: Recommended actions in this release follow a naive heuristic — the dashboard cannot guarantee that executing a recommendation will improve coverage, only that the recommendation addresses an observed gap.

Last updated

Was this helpful?