-
Notifications
You must be signed in to change notification settings - Fork 358
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-7643] β Support VPC IPv4 Ranges in Linode Create flow #10116
feat: [M3-7643] β Support VPC IPv4 Ranges in Linode Create flow #10116
Conversation
β¦re flag so the link disappears once we turn off the feature flag for GA
β¦ field tied to it only if a linode has been selected
β¦ved schema limit on how many IP ranges can be provided; added prop to <Autocomplete /> in LinodeSelect.tsx to prevent 'The value provided to Autocomplete is invalid' console error
β¦put placeholder and button text per updated mockups
β¦signIPRanges />; temp skip in SubnetAssignLinodesDrawer.test.tsx and remove some assertions given changed behavior
β¦splayed in PrimaryNav (linode#10090)
β¦Id; unit test adjustment
β¦imited to 1 element
β¦cription (fixes it across the various views it appears in)
9c47dde
to
4ae0234
Compare
β¦d 'VPC IPv4 Ranges' column to inner Subnets table on VPC Detail page
packages/manager/src/features/VPCs/VPCDetail/SubnetLinodeRow.tsx
Outdated
Show resolved
Hide resolved
@@ -294,6 +305,31 @@ const getIPv4Link = (configInterface: Interface | undefined): JSX.Element => { | |||
); | |||
}; | |||
|
|||
// determineNoneSingleOrMultipleWithChip | |||
const getIPRangesCellContents = ( |
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.
There could be some refactoring between getSubnetLinodeIPv4CellString
and this function since they both accept the same arguments/data.
One other relatively small thing here is making sure the ranges get picked up in the CLI arguments |
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.
This is looking good - confirmed payload has added ranges and everything shows up in VPC detail table.
We'll need to test 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.
@bnussman-akamai Noted, I'll create a follow ticket. Looks like it could use some work in the other drawers too. |
@bnussman-akamai @jaalah Created M3-7709 to look into the error handling |
2d5eca9
into
linode:staging-off-release
Coverage Report: β
|
Description π
Add support for VPC IPv4 Ranges in the Linode Create flow.
ip_ranges
in creation payloadThe inclusion of a "VPC IPv4 Ranges" column in the VPC Detail > Subnets inner table as per the mockups slipped through the cracks during ticket creation, but I noticed it and included it in this PR (to try to keep things more consolidated).
Changes π
Preview π·
How to test π§ͺ
Verification steps
With the
vpc-extra-beta
tag on your account, enter the Linode Create flow and confirm:ip_ranges
propertyAs an Author I have considered π€