Add governed ALZ release promotion
This commit is contained in:
@@ -1498,6 +1498,45 @@ Datasets. `--force` refreshes retained evidence but cannot silently replace a
|
||||
conflicting persisted annual checksum. Use `--scope mol` for an independent
|
||||
municipal series.
|
||||
|
||||
### Governed future definitive ALZ release
|
||||
|
||||
Run the four phases only inside the GeoIntel container. The project id must
|
||||
belong to `Kempen Regional Workbench`:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/manage_alz_agriculture_release.py plan \
|
||||
--project-id <KEMPEN_PROJECT_ID> --refresh-catalog
|
||||
|
||||
docker exec geointel python /app/scripts/manage_alz_agriculture_release.py stage \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--confirm-edition <YYYY-v3_FROM_PLAN>
|
||||
|
||||
docker exec geointel python /app/scripts/manage_alz_agriculture_release.py review \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--confirm-edition <YYYY-v3_FROM_PLAN> \
|
||||
--confirm-plan-sha256 <SHA256_FROM_STAGE> \
|
||||
--approve --reviewer "<OPERATOR_NAME>" \
|
||||
--review-note "Schema, gewascodes, scope en jaarverschillen nagekeken"
|
||||
|
||||
docker exec geointel python /app/scripts/manage_alz_agriculture_release.py apply \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--confirm-edition <YYYY-v3_FROM_PLAN> \
|
||||
--confirm-plan-sha256 <SHA256_FROM_STAGE> \
|
||||
--confirm-review-sha256 <SHA256_FROM_REVIEW>
|
||||
```
|
||||
|
||||
`plan` is read-only. `stage` derives the exact archive from the official
|
||||
catalog campaign/publication date, downloads within the 250 MiB ceiling and
|
||||
runs the existing provisioner with `--force --fetch-only`. The staged plan
|
||||
binds archive, GeoJSON, schema, CRS, crop-code list, scope counts and previous
|
||||
definitive-edition manifest hash/deltas. ZIP member count and extracted size
|
||||
are bounded before the GeoPackage is read. `review` imports nothing. `apply` revalidates the
|
||||
catalog and every byte before using the canonical Dataset upload route.
|
||||
|
||||
Only a definitive `YYYY-v3` is eligible. Current or older editions, v1/v2
|
||||
snapshots, changed catalog/source evidence and paths outside the governed
|
||||
roots fail closed. Existing annual Datasets remain immutable and queryable.
|
||||
|
||||
## Buildings and Addresses Register snapshot
|
||||
|
||||
Prepare and audit the current official Mol snapshot without persistence:
|
||||
|
||||
Reference in New Issue
Block a user