Import rail-kubernetes lifecycle tooling
This commit is contained in:
parent
303be3928e
commit
f31064a3ba
11 changed files with 2010 additions and 12 deletions
|
|
@ -8,7 +8,7 @@ status: active
|
|||
owner: codex
|
||||
topic_slug: railiance
|
||||
created: "2026-07-25"
|
||||
updated: "2026-07-25"
|
||||
updated: "2026-07-26"
|
||||
state_hub_workstream_id: "1f2254f5-a873-46fc-a77c-bc725eeaaeb8"
|
||||
---
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ contract summary.
|
|||
|
||||
```task
|
||||
id: RAIL-K8S-WP-0001-T02
|
||||
status: progress
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "148276a2-2e40-4d56-89dd-2930c5e4309c"
|
||||
```
|
||||
|
|
@ -86,6 +86,15 @@ supporting docs are still pending.
|
|||
`docs/railiance-run-command.md`. Helper scripts and command implementations
|
||||
remain pending.
|
||||
|
||||
2026-07-26: Imported the remaining reviewed helper surfaces from
|
||||
`railiance-cluster`: `tools/create_railiance_overlay_repo.sh`,
|
||||
`tools/cmd/railiance-run`, `tools/cmd/railiance-stage2`, and
|
||||
`tools/cmd/railiance-stage3`. Added a rail-local `bin/railiance` dispatcher
|
||||
limited to `create-overlay`, `run`, `deploy`, `observe`, `promote`, and
|
||||
`rollback`, documented `create-overlay`, refreshed the source import plan, and
|
||||
verified the imported surface with `bash -n`, `python3 -m py_compile`, and
|
||||
`bin/railiance help`.
|
||||
|
||||
## T03 - Prepare the compatibility handoff from `railiance-cluster`
|
||||
|
||||
```task
|
||||
|
|
@ -108,7 +117,7 @@ Acceptance:
|
|||
|
||||
```task
|
||||
id: RAIL-K8S-WP-0001-T04
|
||||
status: progress
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "d78b5712-f305-4967-9034-9b9471633755"
|
||||
```
|
||||
|
|
@ -128,5 +137,7 @@ Acceptance:
|
|||
`ownership_repo: railiance-cluster`. The local repo history is now reconciled
|
||||
with the remote bootstrap commit and pushed to
|
||||
`forgejo-remote:coulomb/rail-kubernetes.git`. A targeted live Fabric registry
|
||||
sync was attempted on July 25, 2026, but `http://127.0.0.1:8765` refused the
|
||||
connection, so live registry ingestion remains the only open part of this task.
|
||||
sync initially failed because `http://127.0.0.1:8765` was down, but after
|
||||
starting the local registry service the targeted sync succeeded. Fabric now
|
||||
stores `rail-kubernetes` as a live registered repo with snapshot `id: 96` at
|
||||
commit `4c2b76e3ecc082bc310523bdcd6c660716e4248b`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue