-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[db][protocol] Implement a CostCenter entity to attribute workspace usage to #10788
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
Conversation
@geropl Apologies for rushing into this 🙈 I actually implemented all this before I saw your request for further alignment, which I agree with: #10757 (comment) So, I'm happy to further align on this concept and on naming, then reflect any changes back in this PR. 👍 |
d7ea0e4
to
df56997
Compare
components/gitpod-db/src/typeorm/migration/1655795038249-CostCenter.ts
Outdated
Show resolved
Hide resolved
components/gitpod-db/src/typeorm/migration/1655795038249-CostCenter.ts
Outdated
Show resolved
Hide resolved
components/gitpod-db/src/typeorm/migration/1655795038249-CostCenter.ts
Outdated
Show resolved
Hide resolved
Whoops, looks like this suffered from bit-rot a bit. If anyone would like to pick this up, please feel free to force-push to this branch, or salvage anything that looks useful from it (no need to attribute me 😊). |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
df56997
to
ea85038
Compare
ea85038
to
54914fb
Compare
cc7e6e7
to
d65afc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concise and spot-on - nice! 🧡
How is no-spending limit represented here? |
Description
Implement a CostCenter entity to attribute workspace usage to.
Related Issue(s)
Fixes #10757
How to test
Release Notes
Documentation
Werft options: