[content-service] Remove UsageReport service#12932
Merged
Merged
Conversation
easyCZ
requested review from
corneliusludmann,
csweichel and
geropl
as code owners
September 13, 2022 21:06
easyCZ
force-pushed
the
mp/cs-remove-usage-service
branch
from
September 14, 2022 12:26
b272b4e to
cc38cb3
Compare
Furisto
approved these changes
Sep 14, 2022
adrienthebo
approved these changes
Sep 15, 2022
adrienthebo
left a comment
Contributor
There was a problem hiding this comment.
/hold in case other reviews are needed, since signing off for self-hosted may merge this PR
LGTM
Member
Author
|
/unhold |
svenefftinge
approved these changes
Sep 16, 2022
geropl
approved these changes
Sep 16, 2022
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
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
We originally used the UsageReportService for storing Usage & Billing reports. However, our strategy shifted to use a Ledger-like approach which makes the usage report obsolete.
This PR removes the service from
content-serviceand deprecates its config.In subsequent PR, the following will be cleaned up:
You can check there's no ongoing traffic over the service from this dashboard
Related Issue(s)
Fixes #
How to test
CI Runs
Release Notes
Documentation
Werft options: