Skip to content

[usage] handle reset usage for chargebee #15056

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

Merged
merged 1 commit into from
Nov 30, 2022
Merged

Conversation

svenefftinge
Copy link
Member

Description

With this change chargebee subscriptions that are cancelled can be handled as a cost center, so that when their subscription ends they transition into a fresh free billing cycle with all their previous usage reset (was covered by chargebee).

In a follow up PR, I'm going to create such cost centers when cancellation happens. They will get a very high spending Limit to make sure all their previous usage gets covered when the subscription ends.

Related Issue(s)

See #15055

How to test

Release Notes

NONE

Documentation

Werft options:

  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-integration-tests=all
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

@svenefftinge svenefftinge requested a review from a team November 30, 2022 08:24
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Nov 30, 2022
chargebee subscriptions that are cancelled get a dedicatd cost center
@svenefftinge svenefftinge force-pushed the se/costcenter_chargebee branch from 68b4926 to 2c88044 Compare November 30, 2022 08:48
@roboquat roboquat merged commit 2eead4a into main Nov 30, 2022
@roboquat roboquat deleted the se/costcenter_chargebee branch November 30, 2022 12:08
@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: webapp Meta team change is running in production deployed Change is completely running in production release-note-none size/L team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants