Background
The Deployment UI currently uses three different verbs for the same action — making a given Revision the current one within a Deployment:
- Revision History tab — button label is "Deploy" / "배포", confirm dialog and success toast use the same verb.
- Add Revision modal — checkbox is "Auto-activate after adding" / "추가 후 자동 활성화".
- In-flight state — row tag and detail panel use "Deploying" / "배포중".
This collides with Deployment (the entity noun), producing awkward phrasing like "Deployment에서 revision을 배포한다" and inconsistent UX across surfaces.
Decision
Unify the revision-action vocabulary to "Apply" / "적용" while keeping Deployment as the entity noun.
| Entity |
Deployment |
배포(명사) — unchanged |
| Revision action (button) |
Apply |
적용 |
| Revision action (in-flight) |
Applying |
적용 중 |
| Auto-apply option in modal |
Apply immediately after adding |
추가 후 바로 적용 |
deployment.status.Deploying (Deployment entity lifecycle status from schema enum DEPLOYING) is kept as-is per the entity / revision-action separation rule.
Scope
i18n key renames (resources/i18n/*.json, namespace deployment):
Deploy → Apply
DeployConfirm → ApplyConfirm
DeployDisabled → ApplyDisabled
DeploySuccess → ApplySuccess
Deploying → Applying
DeployingRevisionApplying → ApplyingRevision
DeployingRevisionDetail → ApplyingRevisionDetail
AutoActivate → AutoApply
Component updates (t() call-sites only — no logic changes):
react/src/components/DeploymentAddRevisionModal.tsx
react/src/components/DeploymentRevisionDetail.tsx
react/src/components/DeploymentRevisionHistoryTab.tsx
react/src/components/DeploymentConfigurationSection.tsx
Out of scope:
deployment.status.Deploying — entity lifecycle state from schema enum.
modelService.EditNotAvailableWhileDeploying — legacy namespace, not in this stack.
- Backend / schema changes — UI labels only.
Acceptance criteria
Stack context
Stacks on top of PR #7428 (FR-2901).
JIRA Issue: FR-2902
Background
The Deployment UI currently uses three different verbs for the same action — making a given Revision the current one within a Deployment:
This collides with
Deployment(the entity noun), producing awkward phrasing like "Deployment에서 revision을 배포한다" and inconsistent UX across surfaces.Decision
Unify the revision-action vocabulary to "Apply" / "적용" while keeping
Deploymentas the entity noun.deployment.status.Deploying(Deployment entity lifecycle status from schema enumDEPLOYING) is kept as-is per the entity / revision-action separation rule.Scope
i18n key renames (
resources/i18n/*.json, namespacedeployment):Deploy→ApplyDeployConfirm→ApplyConfirmDeployDisabled→ApplyDisabledDeploySuccess→ApplySuccessDeploying→ApplyingDeployingRevisionApplying→ApplyingRevisionDeployingRevisionDetail→ApplyingRevisionDetailAutoActivate→AutoApplyComponent updates (
t()call-sites only — no logic changes):react/src/components/DeploymentAddRevisionModal.tsxreact/src/components/DeploymentRevisionDetail.tsxreact/src/components/DeploymentRevisionHistoryTab.tsxreact/src/components/DeploymentConfigurationSection.tsxOut of scope:
deployment.status.Deploying— entity lifecycle state from schema enum.modelService.EditNotAvailableWhileDeploying— legacy namespace, not in this stack.Acceptance criteria
deployment.Deploy/deployment.Deploying/deployment.AutoActivateinreact/src/.scripts/verify.shpasses.Stack context
Stacks on top of PR #7428 (FR-2901).
JIRA Issue: FR-2902