feat: move AgentRun deploy truth to UniDesk YAML

2026-06-13 06:01:27 +00:00
parent 8954a48c92
commit 3717becd77
8 changed files with 1918 additions and 47 deletions
@@ -32,6 +32,12 @@ Code may validate that YAML is present, typed, syntactically valid and renderabl

 External formats such as JSON, TOML, env files, Kubernetes YAML, Caddyfile, systemd units or app-specific config files may still be generated or consumed at the edge when the external tool requires them. They are inputs or rendered artifacts, not UniDesk desired-state truth.

+## Service Deployment Declarations
+
+UniDesk-managed service deployment declarations must not live in service repository JSON such as `deploy.json`. A service repository may keep application source, build inputs, migrations, API/spec documentation and app-native runtime config required by the process. Node/lane selection, runtime namespace, image artifact selection, GitOps branch/path, public exposure, external database wiring, Secret mapping, service account, probes, rollout and cleanup settings belong in the owning UniDesk YAML and are rendered by UniDesk CLI.
+
+Generated GitOps YAML, image catalogs, env files, Kubernetes manifests or external tool config may be committed as rendered artifacts when the runtime requires them. They must carry enough provenance to point back to the owning YAML/source commit and must not become a second editable desired-state truth.
+
 ## Architecture Layers

 YAML-first ops uses five layers.