Automatically set a user's usageAttributionId in cases where there is no ambiguity
#10975
Conversation
This file contains hidden or 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
jankeromnes
changed the title
usageAttributionId in cases where there is no ambiguity
jankeromnes
force-pushed
the
jx/auto-re-attribute
branch
2 times, most recently
from
4f0e17c to
330b50f
Compare
jankeromnes
force-pushed
the
jx/auto-re-attribute
branch
from
330b50f to
2ae3173
Compare
jankeromnes
force-pushed
the
jx/auto-re-attribute
branch
from
2ae3173 to
a50d03e
Compare
…am with usage-based billing enabled, automatically re-attribute usage to that team
…eaves that team, reset their selected 'usageAttributionId'
…tribute member usage to that team when the member has no explicit 'usageAttributionId' yet
jankeromnes
force-pushed
the
jx/auto-re-attribute
branch
from
a50d03e to
f1aa0f9
Compare
easyCZ
approved these changes
Jun 29, 2022
roboquat
added
deployed: webapp
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.
Description
Automatically set a user's explicit
usageAttributionIdin cases where there is no ambiguity:usageAttributionId, and they join a team with usage-based billing enabled --> automatically set the user's defaultusageAttributionIdto that teamusageAttributionId, and one of their teams enables usage-based billing --> automatically set the user's defaultusageAttributionIdto that teamusageAttributionIdto a specific team, but they leave this team --> automatically unset the user's defaultusageAttributionIdagainRelated Issue(s)
Fixes #10973
How to test
d_b_workspace_instance.usageAttributionId==user:{YOUR_USER_ID}d_b_workspace_instance.usageAttributionId==team:{TEAM_ID}d_b_workspace_instance.usageAttributionId==user:{YOUR_USER_ID}Release Notes
Documentation
Werft options: