HEAT patches (authoring)
Operators apply patches through Cluster Manager (/api/patches). Developers author patch sources in patches/ and pack them into .heatpatch archives.
Patch kinds
| Kind | Executor | Targets |
|---|---|---|
platform | heat-node-agent | host-os, k3s, container-images, helm, config |
application | cluster-manager | env-assets, features, session-templates, platform-config, datasources |
Manifest schema: models/heat-patch.schema.json.
Author CLI
python tools/patch-author/create_patch.py new
python tools/patch-author/create_patch.py validate
python tools/patch-author/create_patch.py pack <name>Wrapper: deploy/create-patch.sh.
Full developer guide: patches/README.md.
Pack pipeline
- Copies
manifest.json,check.sh,execute.shfrompatches/<name>/. - Builds
payload.tar.gzfrompatches/<name>/payload/(empty archive if missing). - Updates
payload.sha256viadeploy/update-patch-manifest-hash.mjs. - Writes
dist/patches/<name>.heatpatch.
Runtime (scratch)
Cluster-manager unpacks uploads to scratch:
patches/inbox/— uploaded.heatpatchfilespatches/catalog/<name>/— extracted manifest and scriptspatches/state/<name>.json— application patch apply statepublic/— static env assets (/env-assets)
See references/lovable/cluster-manager/31-patches-and-scratch.md.
Related
- Host agents and platform patch execution:
28-host-agents-and-patches.md - Scratch volume and hxefs:
30-scratch-volume-and-hxefs.md