Making less specific to GCS notifications… #2
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.
…but still supporting the original message format passed to handlers.
There now two kinds of subscriptions:
:clj-gcp.pub-sub.core/subscriber
:pubsub/ack-id
,:pubsub/attributes
and the new:pubsub/payload
which is the UTF-8 value of the notification.:clj-gcp.pub-sub.core/notification-subscriber
:clj-gcp.pub-sub.core/subscriber
which involved json decoding the message payload and merging the attributes and ack-id into the result in mapExisting users of the library should be able to just change to use
:clj-gcp.pub-sub.core/notification-subscriber
.N.B. this has not been extensively integration tested