-
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
upcoming: [M3-7220, M3-7355] - Add DC Get Well logic to various user flows pt2 and cleanup #9945
Conversation
React.useEffect(() => { | ||
if (filteredRegions.length === 1 && !selectedRegionID) { | ||
setSelectedRegionID(filteredRegions[0].id); | ||
} | ||
}, [filteredRegions, selectedRegionID]); |
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.
Deleted this logic to preselect a region if there's only one region with kubernetes capability: we've moved the region filtering logic inside the RegionSelect (filteredRegions
is no longer declared). We can't preselect a region anymore because we can no longer assume that all regions in regionsData
have Kubernetes as a capability, even if regionsData.length
=== 1.
…required prop comments in pt2
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 great
- confirmed the proper behavior for those services RegionSelects ✅
- confirmed comments and cleanups ✅
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, thanks Connie! Confirmed the flows in your description. Thanks for the thorough doc comments too!
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.
Without the MSW (and with/without the DC get well feature flag), for Kubernetes and VPCs:
- Creation flow for each entity still works as expected ✅
- This branch has the same regions as prod ✅
- Tokyo no longer appears in this PR bc we've removed fake regions ✅
- Order of continent/regions may not be the same, we've alphabetized everything ✅
With the MSW + dc get well feature flag, for Kubernetes only:
Disabled regions appear as expected for each entity/capability ✅
If a region doesn't have a capability for some entity, that region doesn't appear ✅
Clicking on the "learn more" link takes you to https://www.linode.com/global-infrastructure/availability ✅
* Only use `undefined` for situations where there is no relevant capability for the RegionSelect - this will not filter any of the regions passed in. | ||
* Otherwise, a capability should always be passed in. | ||
* | ||
* See `ImageUpload.tsx` for an example of a RegionSelect with an undefined `currentCapability` - there is no capability associated with Images yet. |
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 is no capability associated with Images yet" -- is this something API is planning on adding?
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 not completely sure to be honest. Images is currently out of scope, but we'll make a backlog ticket to ask API about this soon
Edit: M3-7525
Description 📝
Preview 📷
kubernetes msw
How to test 🧪
Prerequisites
Verification steps
Without the MSW (and with/without the DC get well feature flag), for Kubernetes and VPCs
With the MSW + dc get well feature flag, for Kubernetes only
As an Author I have considered 🤔
Check all that apply