@rizom/ops 0.2.0-alpha.371 → 0.2.0-alpha.372
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -1
- package/dist/brains-ops.js +2 -2
- package/dist/deploy.js +33 -21
- package/dist/entries/deploy.d.ts +1 -0
- package/dist/image-inventory.d.ts +4 -0
- package/dist/image-types.d.ts +7 -0
- package/dist/images.d.ts +8 -10
- package/dist/index.js +173 -161
- package/package.json +1 -1
- package/templates/rover-pilot/.github/workflows/build.yml +2 -2
- package/templates/rover-pilot/.github/workflows/deploy.yml +3 -0
- package/templates/rover-pilot/README.md +1 -1
- package/templates/rover-pilot/deploy/scripts/verify-runtime-image.ts +18 -0
- package/templates/rover-pilot/docs/operator-playbook.md +15 -2
package/README.md
CHANGED
|
@@ -4,7 +4,11 @@ Operator CLI package for managing pilot brain fleet registry repos.
|
|
|
4
4
|
|
|
5
5
|
## Runtime images
|
|
6
6
|
|
|
7
|
-
The fleet builds one immutable `brain-${brainVersion}` image per effective Brain version.
|
|
7
|
+
The fleet builds one immutable `brain-${brainVersion}` image per effective Brain version. Every new image includes the union of exact site and theme package pins across the entire fleet, including users still running older Brain versions. Smoke-to-fleet promotion therefore reuses the same image without changing package pins or publishing another Brain release. Conflicting pins fail before build, even across cohorts on different Brain versions.
|
|
8
|
+
|
|
9
|
+
Before reusing an existing image, Build verifies its actual installed Brain and package versions against its current adopters. Deploy independently verifies the selected instance's requirements before provisioning or replacing containers, including manual deploys. Verification runs only a manifest-reading command in a read-only, network-disabled container on the CI runner; it never starts the Brain or mounts fleet data. Missing packages, mismatched versions, and verification failures stop the workflow. Existing images are not required to serve cohorts that have not adopted them yet.
|
|
10
|
+
|
|
11
|
+
Explicit builds also load the fleet registry and include its complete package union; `site_packages` adds extra exact pins rather than replacing the union. Package-set changes after an image was published may make that immutable image unsuitable: the gates reject reuse rather than silently rebuilding it. Recovery of an already deployed incomplete image requires a separately reviewed artifact recovery plan.
|
|
8
12
|
|
|
9
13
|
## Commands
|
|
10
14
|
|