Deploy V1 — Overview
The original install path — no manifest, no tasks: one artifact, installed directly. This is what agent 1.5 runs; Deploy V2 is the newer, manifest-driven engine that later agent versions add alongside it.
How the agent picks V1
This is the fallback: if a release's delivered artifacts directory has no install.yaml,
the agent deploys it the V1 way instead of handing off to
Deploy V2.
What V1 checks before installing
Unlike V2 (which does its own checks internally), V1's own code path explicitly:
- Confirms the release's catalog ID is actually in this device type's offering tree — refuses otherwise
- Enforces policy evaluation at the deploy stage, if policy enforcement is turned on for that
stage (
ENFORCE_POLICIES/ enforcement mode) — a failed policy blocks the deploy with the failure reason