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

[UBP] Configure higher usage limit on "Gitpod for Open Source" plan users #14819

Closed
Tracked by #14969
jldec opened this issue Nov 21, 2022 · 5 comments
Closed
Tracked by #14969
Assignees
Labels
feature: billing team: webapp Issue belongs to the WebApp team

Comments

@jldec
Copy link
Contributor

jldec commented Nov 21, 2022

Gitpod for Open Source plan users will receive a higher credit allowance under UBP. This higher usage limit setting should persist indefinitely (not expire at the end of the month)

The Current plan should be labeled “Open Source”.

Besides the difference in plan name and higher credit limit, the Billing page should behave just like other Free-tier users.

See RFC (internal)

nice to have

Showing a one time notification in the dashboard, announcing the switch, and the higher limit would help to improve awareness of the changes.

@jldec jldec added team: webapp Issue belongs to the WebApp team feature: billing labels Nov 21, 2022
@jldec jldec moved this to Scheduled in 🍎 WebApp Team Nov 23, 2022
@jldec
Copy link
Contributor Author

jldec commented Nov 23, 2022

@geropl, @svenefftinge could you confirm that this approach makes sense.

@svenefftinge svenefftinge self-assigned this Nov 24, 2022
@svenefftinge svenefftinge moved this from Scheduled to In Progress in 🍎 WebApp Team Nov 25, 2022
@jldec jldec changed the title [UBP] Auto-configure higher usage limit on "Gitpod for Open Source" plan users when they are enabled for UBP [UBP] Configure higher usage limit on "Gitpod for Open Source" plan users Nov 25, 2022
@svenefftinge
Copy link
Member

The SQL query is in #14950 and should be manually applied.

@jldec
Copy link
Contributor Author

jldec commented Nov 28, 2022

If we're going to it manually, I think it would be nice to do it 2 steps

  1. identify cost centers to be adjusted (or not) to filter out users who already have a higher usage limit
  2. apply the insert, respecting the output of step 1

This makes the 2nd part a little bit safer, using step 1 as a sanity check, and allows the process to be run multiple times without creating duplicates. It also avoids overwriting manually-updated higher usage limits.

@svenefftinge
Copy link
Member

You could verify the select part once more (I did that already). And when it is good, we can apply it.

@jldec jldec moved this from In Progress to In Validation in 🍎 WebApp Team Dec 1, 2022
@jldec
Copy link
Contributor Author

jldec commented Dec 1, 2022

This was done using a manual migration today.
See followup issue #15095

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: billing team: webapp Issue belongs to the WebApp team
Projects
Status: Done
Development

No branches or pull requests

2 participants