feat(FR-2838): show private-deployment alert with access-token shortcut on deployment detail#7294
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has required the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Pull request overview
Adds a page-level “private deployment” notification to the Deployment Detail page (with a shortcut to the Access Tokens section), while refactoring deployment-level alerts and the “Add Revision” modal/refresh state so they live at the page scope instead of inside the configuration cards.
Changes:
- Show an info alert when a deployment is private (
openToPublic === false) and not destroying, including a “Manage Access Tokens” action that smooth-scrolls to#deployment-access-tokens. - Lift deployment-level alerts and the add-revision modal / refetch keys up to
DeploymentDetailPage, passing the necessary refetch/add-revision handlers down intoDeploymentConfigurationSection. - Add i18n strings for the new private-deployment alert title/description and the “Manage Access Tokens” action across supported locales.
Reviewed changes
Copilot reviewed 23 out of 23 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| react/src/pages/DeploymentDetailPage.tsx | Adds private-deployment alert + smooth-scroll action, and hosts page-level alerts/modals/refetch state. |
| react/src/components/DeploymentConfigurationSection.tsx | Refactors to accept fetch keys/refetch/add-revision callbacks from the page instead of owning them locally. |
| resources/i18n/en.json | Adds new deployment alert/action strings. |
| resources/i18n/de.json | Adds new deployment alert/action strings. |
| resources/i18n/el.json | Adds new deployment alert/action strings. |
| resources/i18n/es.json | Adds new deployment alert/action strings. |
| resources/i18n/fi.json | Adds new deployment alert/action strings. |
| resources/i18n/fr.json | Adds new deployment alert/action strings. |
| resources/i18n/id.json | Adds new deployment alert/action strings. |
| resources/i18n/it.json | Adds new deployment alert/action strings. |
| resources/i18n/ja.json | Adds new deployment alert/action strings. |
| resources/i18n/ko.json | Adds new deployment alert/action strings. |
| resources/i18n/mn.json | Adds new deployment alert/action strings. |
| resources/i18n/ms.json | Adds new deployment alert/action strings. |
| resources/i18n/pl.json | Adds new deployment alert/action strings. |
| resources/i18n/pt.json | Adds new deployment alert/action strings. |
| resources/i18n/pt-BR.json | Adds new deployment alert/action strings. |
| resources/i18n/ru.json | Adds new deployment alert/action strings. |
| resources/i18n/th.json | Adds new deployment alert/action strings. |
| resources/i18n/tr.json | Adds new deployment alert/action strings. |
| resources/i18n/vi.json | Adds new deployment alert/action strings. |
| resources/i18n/zh-CN.json | Adds new deployment alert/action strings. |
| resources/i18n/zh-TW.json | Adds new deployment alert/action strings. |
Merge activity
|
…ut on deployment detail (#7294) Resolves #7293 ([FR-2838](https://lablup.atlassian.net/browse/FR-2838)) > Stacked on #7287 (FR-2834). <img width="1231" height="601" alt="image" src="https://github.com/user-attachments/assets/b59e6692-6a8d-4b4e-95ff-3d3852c4db6d" /> ## Summary - Show an info `Alert` on the deployment detail page when the deployment is private (`openToPublic === false`) and not destroying. The alert names the state and offers a "Manage Access Tokens" action that smooth-scrolls to the access tokens section (`#deployment-access-tokens`). - Lifted all deployment-level alerts (`DeploymentReady`, `NoCurrentRevisionDeployed`, `PrivateDeployment`) and the `DeploymentAddRevisionModal` from `DeploymentConfigurationCards` up to `DeploymentDetailPage` so they live where they semantically belong (page-wide notifications, not tied to the configuration cards). - Lifted the page-level `fetchKey` / `revisionFetchKey` / refresh transition state to `DeploymentDetailPage`. `DeploymentConfigurationSection` now receives them via props and exposes `onAddRevision` for both the alert and the section's own "Add Revision" tab-bar button. - Added new i18n keys (`deployment.PrivateDeploymentAlertTitle`, `deployment.PrivateDeploymentAlertDescription`, `deployment.ManageAccessTokens`) across all 22 supported languages. ## Test plan - [ ] On a public deployment detail page, verify no private alert is shown. - [ ] On a private (`openToPublic = false`) deployment, verify the info alert appears with the expected title and description. - [ ] Click "Manage Access Tokens" and verify the page scrolls smoothly to the access tokens section. - [ ] Verify alert ordering is: DeploymentReady → NoCurrentRevisionDeployed → PrivateDeployment. - [ ] Verify the existing "Add Revision" tab-bar button in the configuration section still opens the AddRevision modal (now hosted by the page). - [ ] Verify the refresh button in the configuration overview still works and propagates the loading state. - [ ] On a destroying/stopped deployment, verify the private alert is suppressed. - [ ] Spot-check at least Korean, Japanese, and one Latin-script locale to confirm new keys are translated. [FR-2838]: https://lablup.atlassian.net/browse/FR-2838?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
8a5a711 to
18d3fe9
Compare
c0edb01 to
d5f78df
Compare
Coverage Report for react-coverage (./react)
File Coverage
|
||||||||||||||||||||||||||||||||||||||||||||

Resolves #7293 (FR-2838)
Summary
Alerton the deployment detail page when the deployment is private (openToPublic === false) and not destroying. The alert names the state and offers a "Manage Access Tokens" action that smooth-scrolls to the access tokens section (#deployment-access-tokens).DeploymentReady,NoCurrentRevisionDeployed,PrivateDeployment) and theDeploymentAddRevisionModalfromDeploymentConfigurationCardsup toDeploymentDetailPageso they live where they semantically belong (page-wide notifications, not tied to the configuration cards).fetchKey/revisionFetchKey/ refresh transition state toDeploymentDetailPage.DeploymentConfigurationSectionnow receives them via props and exposesonAddRevisionfor both the alert and the section's own "Add Revision" tab-bar button.deployment.PrivateDeploymentAlertTitle,deployment.PrivateDeploymentAlertDescription,deployment.ManageAccessTokens) across all 22 supported languages.Test plan
openToPublic = false) deployment, verify the info alert appears with the expected title and description.