Skip to content

River post usage

Placeholder James Hochadelrequested to merge
river-post-usage into main

Changes proposed in this pull request:

  • Add river job to post usage at month end. "Post usage" calculates the microcredits consumed by each measurement in the month, updates the measurements with them, then sums them up by customer and transacts against each customers' accounts.
  • Refactor river client initialization to accommodate the new job.

Things to check

  • For any logging statements, is there any chance that they could be logging sensitive data?
  • Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations

None.

Merge request reports