49 lines
2.9 KiB
Markdown
49 lines
2.9 KiB
Markdown
# Near-Term Production Service Lanes Status
|
|
|
|
Updated: 2026-06-27
|
|
|
|
## Purpose
|
|
|
|
Track `CUST-WP-0051-T05`: finish or park near-term production service lanes
|
|
before starting larger migrations.
|
|
|
|
## Lane Board
|
|
|
|
| Lane | Current state | Next action |
|
|
| --- | --- | --- |
|
|
| `issue-wp-0003` | issue-core is live through ArgoCD; image `0.2.1`, Service port `8765`, ExternalSecret Ready, authenticated smoke created Gitea issue `175`. | Do not flip activity-core blindly. First inject `ISSUE_CORE_API_KEY` into `actcore-runtime-secret` through route `activity-core-issue-sink`; then set activity-core `ISSUE_CORE_URL` to port `8765`, set `ISSUE_SINK_TYPE=rest`, restart/sync, and run one safe emission smoke. |
|
|
| `rail-ho-wp-0005` | Forgejo migration remains pre-implementation. Inventory is in progress; production decisions, SMTP/email recovery, cutover, and legacy retirement are human-gated. | Resolve T02 production decisions first, then build the disposable Forgejo probe. Do not start production cutover before promotion lifecycle, email recovery, package registry, Actions, backup/restore, and migration drill pass. |
|
|
| `artifact-store-wp-0007` | All tasks are still `todo`; no live secret gate is currently recorded. | Start with D7.1 fork/object-store landscape and D7.2 compatibility harness. Route D7.3 STS credential vending to NetKingdom if implementation belongs outside artifact-store. |
|
|
| `staged-promotion-lifecycle` | Finished. Lifecycle spec, app contract, overlay scaffold, Stage 1 runner, canary template, deploy/observe tooling, promote/rollback tooling, and onboarding guide are done. | Use the finished promotion gates as prerequisites for Forgejo/source-forge and storage production work. |
|
|
|
|
## Credential And Operator Routing
|
|
|
|
`activity-core -> issue-core` REST emission uses route catalog id
|
|
`activity-core-issue-sink`.
|
|
|
|
Route lookup on 2026-06-27:
|
|
|
|
- owner: `activity-core + issue-core`
|
|
- ops-warden executes: no
|
|
- status: active
|
|
- next action: follow `ops-warden/wiki/playbooks/activity-core-issue-sink.md#worker-checklist`
|
|
|
|
No secret value was read or written. The required non-secret evidence is:
|
|
|
|
- `actcore-runtime-secret` has an `ISSUE_CORE_API_KEY` data key;
|
|
- activity-core worker consumes `ISSUE_CORE_URL=http://issue-core.issue-core.svc.cluster.local:8765`;
|
|
- `ISSUE_SINK_TYPE=rest`;
|
|
- one known-safe activity-core emission returns issue-core HTTP 201 and creates
|
|
a Gitea issue.
|
|
|
|
## Pickup Order
|
|
|
|
1. Close the issue-core handoff gate because the service is already healthy and
|
|
only activity-core live emission remains.
|
|
2. Treat staged-promotion as complete; use it as the gate model before
|
|
Forgejo cutover work accelerates.
|
|
3. Run artifact-store D7.1/D7.2 as an assessment/build harness lane, with D7.3
|
|
routed to NetKingdom if STS vending is not artifact-store-owned.
|
|
4. Keep Forgejo production cutover parked behind explicit T02 decisions and the
|
|
staged-promotion/backup/email/package/action gates.
|