feat(event): handle in advance using source metadata payload #496
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
vincent-pochet
force-pushed
the
misc-kafka-event-metadata
branch
from
dead8e5 to
22b14cf
Compare
jdenquin
approved these changes
Mar 21, 2025
vincent-pochet
force-pushed
the
misc-kafka-event-metadata
branch
from
4d116f4 to
21def8f
Compare
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.
This PR is related to getlago/lago-api#3364
It check the presence of the
ApiPostProcessin the event'sSourceMetadatato check if the enriched events should be sent back to the API events consumer via kafka to process the pay in advance logic.