(plan) clean off the argocd out of date confusion
This commit is contained in:
@@ -5,5 +5,5 @@ Stage: GREEN
|
||||
|
||||
Depends on: [3.2](3.2-delivery-component-test.md), [3.4](3.4-api-delivery.md), [3.5](3.5-api-delivery-resources.md)
|
||||
|
||||
- [ ] Frontend: React Flow, wave columns left->right from `sync-wave` annotations. Click app -> side panel with `react-arborist` virtualized resource tree, lazy-loaded children
|
||||
- [ ] Frontend: React Flow, wave columns left->right from a deployment-wave field. Click app -> side panel with `react-arborist` virtualized resource tree, lazy-loaded children
|
||||
- [ ] Fetch from [/api/delivery](../app/api/delivery/route.ts) and [/api/delivery/{app}/resources](<../app/api/delivery/[app]/resources/route.ts>) (mock) instead of importing `clusterMock` directly
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# 3.7 — Live sync animation (mock, GREEN)
|
||||
# 3.7 — Live deploy-status animation (mock, GREEN)
|
||||
|
||||
Phase: 3 — Delivery Tree (Surface E)
|
||||
Stage: GREEN
|
||||
|
||||
Depends on: [2.5](2.5-api-stream.md), [3.6](3.6-frontend-wave-columns.md)
|
||||
|
||||
- [ ] Live sync animation `OutOfSync -> Syncing -> Synced` driven by [/api/stream](../app/api/stream/route.ts) `delivery` event type (add this event type alongside the existing `topology` one)
|
||||
- [ ] Live status animation `Pending -> Deploying -> Deployed` driven by [/api/stream](../app/api/stream/route.ts) `delivery` event type (add this event type alongside the existing `topology` one)
|
||||
|
||||
Mock only: `/api/stream` emits synthetic deltas, not a real Argo Application watch. See [REQUIREMENTS.md](REQUIREMENTS.md).
|
||||
Mock only: `/api/stream` emits synthetic deltas, not a real deployment-status watch. See [REQUIREMENTS.md](REQUIREMENTS.md).
|
||||
|
||||
## Verify
|
||||
|
||||
|
||||
@@ -6,4 +6,4 @@ Stage: GREEN
|
||||
Depends on: [4.4](4.4-api-exec.md)
|
||||
|
||||
- [ ] [app/cluster/terminal/page.tsx](../app/cluster/terminal/page.tsx) currently has its own inline `run()` command parser — replace it with a `fetch('/api/exec', { method: 'POST', body: JSON.stringify({ cmd }) })` call so the terminal actually round-trips through the mock API instead of simulating client-side
|
||||
- [ ] [components/InteractiveTerminal.tsx](../components/InteractiveTerminal.tsx) (the floating Cmd+K terminal) is a separate, older component with its own hardcoded `commands` map (`kubectl`, `terraform`, `argocd`, `kafka` — all backend/infra flavored) — decide whether to retire it, or reduce it to the same closed command set as the Surface C terminal and wire it to `/api/exec` too
|
||||
- [ ] [components/InteractiveTerminal.tsx](../components/InteractiveTerminal.tsx) (the floating Cmd+K terminal) is a separate, older component with its own hardcoded `commands` map — several entries are named after infra/ops tools with no portfolio relevance — decide whether to retire it, or reduce it to the same closed command set as the Surface C terminal and wire it to `/api/exec` too
|
||||
|
||||
+2
-2
@@ -1,7 +1,7 @@
|
||||
# riotpiao — Task Board (Next.js portfolio, mock-backed)
|
||||
|
||||
This repo is scoped to the Next.js portfolio frontend only. Anything requiring `kubectl`, a real cluster, a Go
|
||||
backend, or infra-side config (Cloudflare, GitOps, RBAC) has been moved to [REQUIREMENTS.md](REQUIREMENTS.md) —
|
||||
backend, or infra-side config (Cloudflare, deployment pipelines, RBAC) has been moved to [REQUIREMENTS.md](REQUIREMENTS.md) —
|
||||
a handoff spec for whoever builds the real `atlas` backend service. The four cluster-visualization surfaces
|
||||
(topology, delivery, terminal, chat) run against mock `/api/*` Next.js route handlers backed by
|
||||
[lib/clusterMock.ts](../lib/clusterMock.ts) fixture data.
|
||||
@@ -42,7 +42,7 @@ Rules carried from the ADR (frontend-relevant subset):
|
||||
| [3.4](3.4-api-delivery.md) | GET /api/delivery (mock, GREEN) — done |
|
||||
| [3.5](3.5-api-delivery-resources.md) | GET /api/delivery/{app}/resources (mock, GREEN) — done |
|
||||
| [3.6](3.6-frontend-wave-columns.md) | Frontend: wave columns + resource tree (GREEN) |
|
||||
| [3.7](3.7-live-sync-animation.md) | Live sync animation (mock, GREEN) |
|
||||
| [3.7](3.7-live-sync-animation.md) | Live deploy-status animation (mock, GREEN) |
|
||||
| [3.9](3.9-simplify-pass.md) | simplify skill pass (REFACTOR) |
|
||||
| [3.10](3.10-landing-page-cleanup.md) | Landing page: remove fabricated stats and dead links (GREEN) |
|
||||
|
||||
|
||||
+1
-1
@@ -16,7 +16,7 @@ Mock API layer implemented. Remaining: wire page components to fetch from it, RE
|
||||
|
||||
Task board lives in [INDEX.md](INDEX.md) — one row per task, one file per task (`<id>-<slug>.md`), agent-harness format. That file is the source of truth for execution order; this README is a human overview only.
|
||||
|
||||
Everything cluster/backend/infra (GitOps, DNS, RBAC, the real `atlas` Go service, rate-limiting tiers 1-3, observability) is out of scope for this repo — see [REQUIREMENTS.md](REQUIREMENTS.md), a handoff spec for whoever builds that separately.
|
||||
Everything cluster/backend/infra (deployment pipelines, DNS, RBAC, the real `atlas` Go service, rate-limiting tiers 1-3, observability) is out of scope for this repo — see [REQUIREMENTS.md](REQUIREMENTS.md), a handoff spec for whoever builds that separately.
|
||||
|
||||
| Phase | Description |
|
||||
|---|---|
|
||||
|
||||
Reference in New Issue
Block a user