Add billing to device lifecycle #970
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Steve-Mcl
reviewed
Sep 12, 2022
Co-authored-by: Stephen McLaughlin <44235289+Steve-Mcl@users.noreply.github.com>
Steve-Mcl
reviewed
Sep 12, 2022
|
I have now added the final test for deviceFreeAllocation. |
Prompt user to confirm per-device charge when registering charge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #782
This adds a billing step to the device lifecycle.
If
billing.stripe.device_product/device_priceare set, then whenever a device is added/removed from team, the billing subscription item is updated for the team to reflect how many devices are in the team.If the team type includes a
deviceFreeAllocationproperty, this is taken into account when identifying how many 'billable' devices a team has.This PR does not update the UI - that will come in the final PR for this story.