Skip to content

Conversation

@ankita-akamai
Copy link
Contributor

@ankita-akamai ankita-akamai commented Jan 8, 2026

Description 📝

Add delete action for user alert channels.

Changes 🔄

  • Add delete action to the notification channel action menu for user channels
  • Implement delete confirmation dialog using TypeToConfirmDialog component
  • Add delete mutation hook (useDeleteNotificationChannel) with optimistic cache updates
  • Disable delete action when a channel has associated alerts, with a tooltip explaining why
  • Add success and error snackbar notifications for delete operations
  • Add unit tests and mocks.

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

28 Jan 2026

Preview 📷

image image image image

How to test 🧪

Verification steps

https://www.figma.com/design/26kXnWVNU5tK2xQdDdISuC/Custom-Alerts?node-id=7418-38705&t=YhSM9MnUVbY3hAMv-1

  • Navigate to Monitor > Alerts > Notification Channels
  • Open the action menu (three dots) for a user-created notification channel
  • Verify "Delete" action is visible in the menu
  • Click "Delete" and verify the confirmation dialog appears
  • Type the channel label to confirm deletion
  • Verify success snackbar appears after successful deletion
  • Test with a channel that has associated alerts - verify delete is disabled with tooltip
  • Test with a system channel - verify delete action is not shown
  • Test error handling by simulating a failed delete request
Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@ankita-akamai ankita-akamai self-assigned this Jan 8, 2026
@ankita-akamai ankita-akamai marked this pull request as ready for review January 8, 2026 08:01
@ankita-akamai ankita-akamai requested a review from a team as a code owner January 8, 2026 08:01
data-qa-notification-channel-action-cell={`notification-channel-${id}`}
>
<NotificationChannelActionMenu
alertsCount={alerts.length}
Copy link
Contributor

@santoshp210-akamai santoshp210-akamai Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a dependency on this line. Yesterday I merged a PR to the release branch directly. #13254. It contains the changes regarding the latest API specification changes for Notification Channels. So this will break when the API changes.

So will hold off on merging this PR until the release is back-merged .

React.useState<NotificationChannel | null>(null);
const [deleteState, setDeleteState] = React.useState({
isDialogOpen: false,
isDeleting: false,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Managing isDeleting in state is okay but may be unnecessary. The useDeleteNotificationChannel mutation hook will return an isPending value that could be used instead to track the loading state.

@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🎉 855 passing tests on test run #4 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
0 Failing855 Passing11 Skipped43m 38s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Review

Development

Successfully merging this pull request may close these issues.

4 participants