milestone 9 completed
This commit is contained in:
@@ -18,6 +18,28 @@ print(r['commit'], r['version'], r['images'])
|
||||
PY
|
||||
```
|
||||
|
||||
The repository verifier performs the same checks strictly, also calculates the release-record checksum used by later acceptance records, and can compare the record with images already loaded on an isolated Docker host:
|
||||
|
||||
```sh
|
||||
python3 deploy/verify_release.py \
|
||||
--archive guestops-images.tar.gz \
|
||||
--record release-record.json \
|
||||
--commit a3ef408de61d895e69516fa3ba014b43621032bc \
|
||||
--version 0.2.0 \
|
||||
--output release-verification.json
|
||||
|
||||
gunzip -c guestops-images.tar.gz | docker load
|
||||
python3 deploy/verify_release.py \
|
||||
--archive guestops-images.tar.gz \
|
||||
--record release-record.json \
|
||||
--commit a3ef408de61d895e69516fa3ba014b43621032bc \
|
||||
--version 0.2.0 \
|
||||
--verify-loaded-images \
|
||||
--output loaded-image-verification.json
|
||||
```
|
||||
|
||||
Retain both verification summaries with the untouched archive, release record, its SHA-256, and the exact default-branch CI metadata. A waiting, cancelled, failed, or branch-only run is not release evidence. Do not substitute a local rebuild for the archived default-branch images.
|
||||
|
||||
Load the archive, verify each loaded image ID matches the record, set `GUESTOPS_API_IMAGE` and `GUESTOPS_WORKER_IMAGE` to the recorded full-SHA references, and run the deployment preflight. Record the CI run, commit, checksum and operator in the change ticket. A release tag is an approval marker; do not move or reuse an existing tag. The application and web versions must match before the record can be created.
|
||||
|
||||
For rollback, first disable worker-driven external writes and reconcile any sending, payment or PMS operation that may have completed since the prior release. Confirm the previous release archive and record are retained, verify its checksum and image IDs, take an encrypted backup, then select the previous recorded image references in `.env` and recreate only the API and worker. Do not roll back MongoDB or the key volume merely to change application images. Run the online preflight, readiness check and read-only smoke test before re-enabling the worker or provider writes. If a release introduced an incompatible data change, follow its release-specific recovery plan rather than starting an older image against newer data.
|
||||
|
||||
Reference in New Issue
Block a user