Closed chambridge closed 5 years ago
I really don't think this is the mechanism that we want. We don't want to trigger a huge amount of DB churn every time someone edits a price. That isn't going to scale at all.
I think we need to discuss what we want before we implement anything.
We could also do a look up the next time we are processing new data to see if any rate changes occurred during the window of the previous processing and if so expand the summarization from 3 day window to the full month. That would avoid us kicking off triggers while a user is actively making multiple edits to rates and just slightly alter what was going to take place anyways during normal processing flow.
This doesn't match our most recent discussion of the price list features. Closing this to remove confusion.
User Story
As user, I want my charges for the month to be recalculated if changes are made during the month so that the reflected charges match the "current" price list.
Impacts
Backend
Role
User
Implementation Details
Endpoint to trigger charge recalculation within a month.
Acceptance Criteria
Related to: https://github.com/project-koku/koku/issues/468