Upgrades page, cluster upgrade history, and stage and organization links in Studio

未关闭
#2,093 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
playwright, react, typescript
领域
frontend

调研方向

Start with the screen design in #2091 and the organization and cluster menu entry points for the Upgrades page, history, and link controls. The work depends on Central Manager routes #1178, #1179, and #1191, upgrade path issues #1187–#1190, and upgrade decision sign-off; review those before estimating implementation. Done means the listed admin controls, read-only member view, hidden-on-404 behavior, co-located Vitest tests, and Playwright coverage meet the acceptance criteria.

由索引模型根据 Issue 内容生成。

描述

Start: Waits for sign-off of the upgrade decisions, and for HarperFast/central-manager#1178, HarperFast/central-manager#1179, HarperFast/central-manager#1187, HarperFast/central-manager#1188, HarperFast/central-manager#1189, HarperFast/central-manager#1190 and HarperFast/central-manager#1191 in Central Manager.
Delivery: in one PR with #2091 and #2092.

What and why

Fabric clusters will be upgraded automatically each month on a slot Harper assigns to the organization (HarperFast/central-manager#1177). Customers need to see and steer that in Studio: when the next upgrade is, which build, which cluster goes first, and what happened before. This issue adds the Upgrades page, the per-cluster upgrade history, and the controls for stage links and organization links.

Scope

  • Upgrades page, in the organization menu. Shows the slot, the next cycle's dates and pinned build, and each cluster's state. Org admins can move a date earlier for this cycle, and, in an organization on the conservative track, turn the hold on or off. GET /UpgradeSchedule, GET and PATCH /UpgradeCycle (HarperFast/central-manager#1191).
  • Upgrade history, in the cluster menu next to Version: versions, dates, source and outcome. GET /Cluster/:id/upgrades (HarperFast/central-manager#1191).
  • Stage link, in cluster settings: pick the production cluster this cluster upgrades before, or clear it. Clusters in linked organizations are offered. PUT /Cluster/:id with upgradeBeforeClusterId (HarperFast/central-manager#1179).
  • Organization link: link or unlink another organization the user also administers. POST /OrganizationLink, DELETE /OrganizationLink/:id (HarperFast/central-manager#1178).
  • Members who are not admins see the page read-only.
  • Everything stays hidden while the routes answer 404 or the mode is off.
  • Follow the screen design in #2091.

Out of scope

  • Notices and notification settings: #2092.
  • Staff pages: #2094.

Depends on decisions

The scope may change with sign-off of the upgrade decisions. If one of these changes, revisit this issue.

  • A customer can move a date for one cycle, earlier only, never later than the slot (D13).
  • Stage and production are at least one business day apart, and a date can be moved until the day before (P1).
  • The conservative-track hold is turned on or off by the org admin and locks when the stage upgrade starts (D49).
  • Org admins and staff can set the stage link (D7).
  • One stage cluster per production cluster at launch (D6).
  • A stage cluster may be in a linked organization (D8).
  • The upgrade history page is in launch scope (D43).
  • Everything ships off and is turned on by configuration (D38).

Depends on

  • HarperFast/central-manager#1178, HarperFast/central-manager#1179, HarperFast/central-manager#1191: the routes these screens call.
  • HarperFast/central-manager#1187 to HarperFast/central-manager#1190: the live upgrade path behind them.
  • #2091: the design document.

Acceptance

  • An org admin can move a date earlier and toggle the hold; the server's refusals (a later date, a locked hold) are shown plainly.
  • History lists each upgrade of the cluster.
  • A stage link can be set and cleared, including to a cluster in a linked organization.
  • Nothing new shows when the routes answer 404.
  • Vitest tests co-located with the components, and Playwright coverage for the Upgrades page.

Part of HarperFast/central-manager#1177.

🤖 Generated by Claude Code (Claude Opus 5.5); posted via @Devin-Holland.

主要语言
TypeScript
星标
5
派生
4
平均合并
2 天 13 小时
30 天内合并 PR
60

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

HarperFast/studio 的其他 Issue

查看 HarperFast/studio 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。