-
Notifications
You must be signed in to change notification settings - Fork 389
poc: [M3-9996, M3-10048] - Assigning alert definitions (beta) to a Linode during creation
#12248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… the Linode details page
...ges/manager/src/features/CloudPulse/Alerts/ContextualView/AlertInfoActionTableCreateFlow.tsx
Outdated
Show resolved
Hide resolved
...ges/manager/src/features/CloudPulse/Alerts/ContextualView/AlertInfoActionTableCreateFlow.tsx
Outdated
Show resolved
Hide resolved
* Merge edit & create logic in action table * make components flexible * update handler func * type correction * optimize state updates * remove unused func * update type * refactor & cleanup
|
A bit concerned about the headers here - |
|
Overall looks good to me, pending @nikhagra-akamai and @venkymano-akamai review |
9f2e358 to
90123d7
Compare
nikhagra-akamai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
beta) to a Linode during creation
@pmakode-akamai can you please elaborate on what these product requirements are? |
@jdamore-linode Yea, Create Flow logic is like:
|
packages/manager/src/features/Linodes/LinodeCreate/utilities.ts
Outdated
Show resolved
Hide resolved
Cloud Manager UI test results🎉 659 passing tests on test run #21 ↗︎
|

Description 📝
An alternative way to ensure alerts are assigned only during the Linode creation process, with RHF integrated to support Create Linode form flow
Important
Note
Additional Optionssection and display Legacy Alerts (read-only) on Create Linode page #12355Changes 🔄
betaAlerts) to a Linode during creationCreateLinodeRequesttype inapiv4packagealertsinCreateLinodeSchemaTarget release date 🗓️
N/A
Preview 📷
How to test 🧪
Prerequisites
MSWand theACLP Integrationfeature flagVerification steps
systemanduseralerts)undefinedor not present or excluded in legacy modeAuthor 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
As an Author, before moving this PR from Draft to Open, I confirmed ✅