feat: allow custom route extractor on pg notify router #1041
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
adityathebe
force-pushed
the
feat/pg-notify-custom-router
branch
from
98b03a9 to
d5cb9fc
Compare
adityathebe
force-pushed
the
feat/pg-notify-custom-router
branch
from
5205c28 to
ab85159
Compare
moshloop
force-pushed
the
feat/pg-notify-custom-router
branch
from
ab85159 to
dee89e6
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.
The notify router expected the pg notify payload to be in format.
We allow consumers to provide custom extractor & let them decided how to extract the route & the actual payload from the original notify payload.
This is required for
playbook_action_updatesPG notify where we extract the route & payload from a JSON payload.