manager
manager copied to clipboard
refactor: [M3-8071] - Rename Edge Regions to Distributed Regions
Description 📝
Effort to bring clarity to new regions and plan offerings
Changes 🔄
- Important: For our
typesand places we're checking forsite_type, we're allowing bothedgeanddistributeduntil the DB/API changes are ready. Then we'll do some cleanup afterwards. - Everywhere we used the term
edgewill now be calleddistributed. - In places where we only used the name/text
edge, I've includedregionfor clarity.- Example:
type SupportedEdgeTypes=>type SupportedDistributedRegionTypes
- Example:
Target release date 🗓️
TBD: We will try to release this in conjunction with API changes
Preview 📷
| Before | After |
|---|---|
| 📷 |
How to test 🧪
Prerequisites
- Pull down branch and ensure
Geckofeature flag is active in dev tools
Reproduction steps
-
Try to create a Linode in an edge/distributed region
-
Observe
edgeshould no longer be shown -
Using MSW, try to migrate an edge/distributed linode to a non-distributed region
-
Observe warnings should be updated
As an Author I have considered 🤔
Check all that apply
- [x] 👀 Doing a self review
- [x] ❔ Our contribution guidelines
- [ ] 🤏 Splitting feature into small PRs
- [x] ➕ 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
- [x] 👣 Providing comprehensive reproduction steps
- [x] 📑 Providing or updating our documentation
- [ ] 🕛 Scheduling a pair reviewing session
- [ ] 📱 Providing mobile support
- [ ] ♿ Providing accessibility support
Coverage Report: ✅
Base Coverage: 82.35%
Current Coverage: 82.35%