-
Notifications
You must be signed in to change notification settings - Fork 373
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
upcoming: [M3-9421] - Add API endpoints and types for /v4/nodebalancers
#11832
base: develop
Are you sure you want to change the base?
upcoming: [M3-9421] - Add API endpoints and types for /v4/nodebalancers
#11832
Conversation
…endpoints for NB-VPC Integration
Coverage Report: ✅ |
nodes: array() | ||
.of(nodeBalancerConfigNodeSchema) | ||
.required() | ||
.min(1, 'You must provide at least one back end node.'), |
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.
we'll need a Validation changed
changeset for this
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.
Removed this change since nodes
are not a required field for updating configs, contrary to what the tech docs mention
…241-add-endpoints-in-nb
…h-akamai/manager into M3-9241-add-endpoints-in-nb
6e2aace
to
aa17b47
Compare
@@ -235,7 +246,7 @@ export interface CreateNodeBalancerPayload { | |||
configs: CreateNodeBalancerConfig[]; | |||
firewall_id?: number; | |||
tags?: string[]; | |||
vpc?: { | |||
vpcs?: { |
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.
Feedback from previous PR comment
Cloud Manager UI test results🎉 539 passing tests on test run #10 ↗︎
|
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, thank you!
* | ||
* @param nodeBalancerId { number } The ID of the NodeBalancer to view vpc config info for. | ||
*/ | ||
export const getNodeBalancerVPCsBeta = ( |
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.
optional: wondering if these should be renamed to getNodeBalancerVPCConfigsBeta since we're getting VPC config data, not VPCs specifically?
either makes sense to me though, especially since the endpoint itself uses /vpcs, not /vpc-configs.
Description 📝
Add new /v4/nodebalancers (& /v4beta/nodebalancers) endpoints for NB-VPC Integration
How to test 🧪
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
As an Author, before moving this PR from Draft to Open, I confirmed ✅