I found your blogpost about the event system
https://killbill.io/blog/persistent-bus-in-kill-bill/In case someone is curious and finds this post i will try and explain what i have found. In case my asumptions are wrong please let me know.
There are 4 tables for the bus events described in the blogpost
The internal ones
bus_events
bus_events_history
The mirrored external ones.
bus_ext_events
bus_ext_events_history
Im guessing the ext ones are used for push notifications
I havent notifced any differences in what gets inserted so it seems like
When events are made they are inserted into bus_events. When they are handled they are deleted bus_events and inserted into bus_events_history.
The different killbill subsystems can subscribe to these events.
There is also invoice_billing_events which i didnt look into
Then there are the two tables related to the subscription events
subscription_event_history
subscription_events
This works in a differnet way. Events are writen to both tables
subscription_event_history keeps all events
If you for example undo a future change the event will be deleted from subscription_events but it will still be in subscription_event_history
--------
I do still have a question
I am seeing some different kind of errors when i try to change a subscription and specify the current date.
It seems to work sometimes. Other times the change does not go through or i get an error.
Are you supposed to be able to specify todays date or should you just not give the date and specify a a billingPolicy of IMMEDIATE or something like that?