Invoice generation through API lacks atomicity about killbill HOT 3 CLOSED

We have a few use case, where we would like to i/ have atomicity and ii/ keep our modularity:

• Invoice creation and chargeThroughDate set in subscription
• Payment creation and update invoicePayment table (even more tricky because this is done from a pseudo-plugin)

The first case could be solved by using internal api similar to what we have for bus (by passing a open transaction). It's a bit of a weird api, but this is al;ready what we do.

from killbill.

• Payment creation and update invoicePayment table (even more tricky because this is done from a pseudo-plugin)

We created #508 to track that work.

• Invoice creation and chargeThroughDate set in subscription

We could either use an internal api similar to what we have for bus (by passing a open transaction) as suggested above or have subscription module listen to bus events to update the chargeThroughDate (but that would be force us to add the chargeThroughDate info inside the event to avoid subscription fetching invoice, which it can't today because of dependency).

from killbill.

See also #282.

from killbill.