Skip to content
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-8581] - GPUv2 M1 Egress Banner #10956

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

abailly-akamai
Copy link
Contributor

@abailly-akamai abailly-akamai commented Sep 17, 2024

Description 📝

Small PR to add a GPUv2 Banner for the 9/30 new GPU plans launch. This is the MVP for the initial launch, before modifying the Plans Panel to account for transfer and billing changes.

Note

This is very much a temp banner, which is the reason for not adding the banner to the existing e2e coverage. It will be removed in an upcoming M2 update.

Changes 🔄

  • Add new egressBanner property to the GPUv2 flag object
  • Add new banner behind flag conditional

Target release date 🗓️

9/30/2024

Preview 📷

Linodes create

How to test 🧪

Important

You may want the gpuv2beta flag on your account to get the new GPUv2 plans to show up, but it is not a requirement for testing the display of the banner

Verification steps

  • Make sure the gpuv2 flag is on
  • Navigate to the Linode Create flow, and verify the following:
    • This notice shall be consistent for the entire length of the promotion regardless of region if the user selects the GPU plan type
    • The notice should display wether the user has picked a region or not
    • This notice shall appear at the top, first sequentially before any other notices as relevant
    • The banner should not impact the logic / display of the other banners

As an Author I have considered 🤔

Check all that apply

  • 👀 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

@abailly-akamai abailly-akamai self-assigned this Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant