-
Notifications
You must be signed in to change notification settings - Fork 367
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
feat: [M3-7487] - Add AGLB Endpoint Health #10008
feat: [M3-7487] - Add AGLB Endpoint Health #10008
Conversation
Coverage Report: ✅ |
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.
@@ -0,0 +1,5 @@ | |||
--- | |||
"@linode/api-v4": Added | |||
--- |
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.
Just to confirm, this isn't an upcoming feature anymore, is it?
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.
I'm going to keep considering it an upcoming feature
until it's in public beta. We're probably a few weeks away from that
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.
I'm going to keep considering it an upcoming feature until it's in public beta.
In that case, should this changeset entry be under Upcoming Features
rather than Added
?
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.
I think I wen't with added
because api-v4 has no way to to "gate" features. Once the code is released, it's "added" to the package
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.
Should it still be Upcoming Features
?
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.
Once the code is released, it's "added" to the package
Yeah, that's fair. I was thinking we'd been putting other AGLB api-v4 work under Upcoming, so suggested it for consistency, but I might be misremembering.
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.
Yeah, I'm not sure. Maybe api-v4 shouldn't have an Upcoming Features
? I'll add a cafe item
|
||
if (!health) { | ||
return <EndpointHealth down={0} up={0} />; | ||
} |
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.
What could health
being undefined mean? Is there anything relevant we'd want to display to the user?
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.
It shouldn't really happen because the loading and error cases are checked before this. This was mostly just to satisfy typescript.
@@ -9,6 +9,7 @@ import { TableRow } from 'src/components/TableRow'; | |||
import { Typography } from 'src/components/Typography'; | |||
import { IPAddress } from 'src/features/Linodes/LinodesLanding/IPAddress'; | |||
|
|||
import { LoadBalancerEndpontHeath } from '../LoadBalancerDetail/LoadBalancerEndpointHealth'; |
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.
Got two typos on your export LoadBalancerEndpontHeath
> LoadBalancerEndpointHealth
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.
Fixed in 36ee5b8, good catch!
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.
Endpoints are visible:
✅ on the Load Balancer Landing page
✅ on the Load Balancer details Summary tab
✅ in the Configurations tab
✅ in the Service Targets table
Edit:
also, more of a UX question, is it worth showing the status icon at all in this case?
I would also be in favor of not showing the status in this case.
There are some small discrepancies in loading and error state:
@@ -0,0 +1,5 @@ | |||
--- | |||
"@linode/api-v4": Added | |||
--- |
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.
I'm going to keep considering it an upcoming feature until it's in public beta.
In that case, should this changeset entry be under Upcoming Features
rather than Added
?
packages/manager/.changeset/pr-10008-upcoming-features-1704919046550.md
Outdated
Show resolved
Hide resolved
expect(upStatusIcon).toHaveStyle({ backgroundColor: '#17cf73' }); | ||
expect(downStatusIcon).toHaveStyle({ backgroundColor: '#ca0813' }); |
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.
Nice!
I think I'm going to show endpoint status at all times because it's often inside a table and I don't think we need to add the complexity of conditionally hiding it. |
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.
because it's often inside a table and I don't think we need to add the complexity of conditionally hiding it.
As long as we don't receive user feedback that it's a reason for visual overwhelm in the table or is somehow confusing to users, I think keeping it is fine.
Thanks for the loading and error state updates - confirmed we no longer see a tiny loader on Summary and the endpoints on Configurations surface an error. ✅
Definitely will reevaluate the error states if they happen often or if we get feedback about them! |
Description 📝
Preview 📷
How to test 🧪
Prerequisites
dev-test-aglb
accountVerification steps
Preview
sectionAs an Author I have considered 🤔