feat: #1686 add Container Config tab skeleton #1705
Reference in New Issue
Block a user
Delete Branch "feat/1686-container-config-tab"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Comprehensive testing performed
canvas: npm test -- --run src/components/__tests__/SidePanel.tabs.test.tsx src/components/tabs/__tests__/ContainerConfigTab.test.tsx src/store/__tests__/canvas.test.ts src/store/__tests__/canvas-topology.test.tscanvas: npm run buildLocal-postgres E2E run
N/A: Canvas-only read-only tab skeleton. No backend schema, SQL, or Postgres behavior changed.
Staging-smoke verified or pending
Pending: PR CI will run the Canvas and staging-canvas checks. No live staging deploy has been triggered from this feature branch.
Root-cause not symptom
#1686 Track B requested a separate Container Config tab so runtime/container settings do not get mixed into the EC2 compute/display shape editor. This adds that separate surface and keeps it read-only until backend edit endpoints exist.
Five-Axis review walked
/workspaceonly.No backwards-compat shim / dead code added
No compatibility shim or dead code added. Existing Config tab remains unchanged; Container tab is a new sibling tab.
Memory/saved-feedback consulted
No saved memory was needed for this slice. Used live #1686 comments, merged PR #1701 state, and repo-local code/tests.
QA approval for #1686 Container Config tab skeleton. Scope is Canvas-only, read-only, separate from compute/display shape editing. Local tests/build and PR CI implementation jobs are green.
Security approval for #1686 Container Config tab skeleton. No backend access expansion, no new network call, no secrets, and host workspace_dir is not surfaced; mounted path is fixed to /workspace.
/sop-ack comprehensive-testing verified local canvas tests/build and PR CI
/sop-ack local-postgres-e2e N/A canvas-only change
/sop-ack staging-smoke staging-canvas PR check passed
/sop-ack root-cause container config separated from compute/display editing
/sop-ack five-axis-review reviewed correctness readability architecture security performance
/sop-ack no-backwards-compat no shim or dead code
/sop-ack memory-consulted live issue/repo context sufficient