coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: add migration export and write fencing
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 19s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 17:07:53 +02:00
parent 9285a880be
commit f6758b91ce
10 changed files with 317 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -47,3 +47,14 @@ retirement, and relocation from CoulombCore to railiance01 are complete.
and eventual archive (`CORE-WP-0010`). Its dual-run design is recorded and S0
is active against published hub-core revision `7e1ec03`, building the durable
backend and internal candidate before any public traffic changes.
Operational migration bundles are emitted without raw key material:
```bash
core-hub-ops migration export --source-revision "$(git rev-parse HEAD)" \
--output core-hub-export.json
```
`CORE_HUB_V2_WRITE_GROUPS` controls legacy write authority for `registry`,
`credentials`, `interaction`, and `deferred`. The deployment package must
remove a group here before enabling the matching hub-core writer.