-
Notifications
You must be signed in to change notification settings - Fork 370
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-7390] - Add AGLB protocol
to Service Targets
#9891
feat: [M3-7390] - Add AGLB protocol
to Service Targets
#9891
Conversation
…teServiceTargetSchema` and `UpdateServiceTargetSchema`
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.
Protocol now shows in the table ✅
Edit a Service Target, you can change the protocol ✅
Create a Service Target, you can pick a protocol ✅
packages/manager/.changeset/pr-9891-upcoming-features-1699549397674.md
Outdated
Show resolved
Hide resolved
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.
Service target protocol is visible in table and in the drawer when adding or editing a service target. 🚢
When we've added table columns, we'd forgotten to update the error state of the table, so we're a couple columns short, I noticed when blocking GET service-targets network requests. I made the suggestions to fix that.
@@ -167,49 +180,13 @@ export const LoadBalancerServiceTargets = () => { | |||
{error && <TableRowError colSpan={6} message={error?.[0]?.reason} />} |
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.
{error && <TableRowError colSpan={6} message={error?.[0]?.reason} />} | |
{error && <TableRowError colSpan={8} message={error?.[0]?.reason} />} |
@@ -167,49 +180,13 @@ export const LoadBalancerServiceTargets = () => { | |||
{error && <TableRowError colSpan={6} message={error?.[0]?.reason} />} | |||
{data?.results === 0 && <TableRowEmpty colSpan={6} />} |
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.
{data?.results === 0 && <TableRowEmpty colSpan={6} />} | |
{data?.results === 0 && <TableRowEmpty colSpan={8} />} |
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.
Any discrepancies with ca_certificate
still in the API spec are because changes are not fully reflected there, correct? (Can we request that they fix?)
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.
LGTM!
- Verify that Protocol now shows in the table
- Verify that when you edit a Service Target, you can change the protocol
- Verify that when you create a Service Target, you can pick a protocol
@@ -0,0 +1,54 @@ | |||
import type { ServiceTargetPayload } from '@linode/api-v4'; |
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.
Any thoughts in naming this file as constants
instead of utils
?
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.
✅ protocol now shows in the table
✅ can change protocol when editing a service target
✅ can pick protocol when creating a service target
awesome job! 🎉
Description 📝
Adds
protocol
support to AGLB certificates based on a change to the API. This PR also makes other Service Target related changes/fixesChanges 🔄
protocol
field to Service Targetsca_certificate
➡️certificate_id
based on API changePreview 📷
How to test 🧪
Prerequisites
Verification steps
Protocol
now shows in the tableAs an Author I have considered 🤔