[usage] Implement ledger control loop #12662
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
easyCZ
force-pushed
the
mp/usage-ledger-control-loop
branch
2 times, most recently
from
9984c45 to
d2626db
Compare
easyCZ
force-pushed
the
mp/usage-ledger-control-loop
branch
from
f389c7e to
5bdc2b5
Compare
roboquat
added
release-note-none
and removed
do-not-merge/release-note-label-needed
labels
svenefftinge
approved these changes
Sep 6, 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
Implement main ledger control loop.
Collects instances and usage records and splits them into inserts and updates. In this PR, the records are not yet persisted but are printed out for verification. Next PR will add persistence to these.
Related Issue(s)
Fixes #
How to test
Unit tests
Release Notes
Documentation
Werft options: