-
Notifications
You must be signed in to change notification settings - Fork 45
feat: Support Pub/Sub push notifications format (adapt to CloudEvent) #238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
10 changes: 10 additions & 0 deletions
10
src/Google.Cloud.Functions.Framework.Tests/GcfEvents/emulator_pubsub.json
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
{ | ||
"subscription": "projects\/emulator-project\/subscriptions\/test-subscription", | ||
"message": { | ||
"data": "VGVzdCBtZXNzYWdlIGZyb20gZW11bGF0b3I=", | ||
"messageId": "1", | ||
"attributes": { | ||
"attr1": "attr-value1" | ||
} | ||
} | ||
} |
12 changes: 12 additions & 0 deletions
12
src/Google.Cloud.Functions.Framework.Tests/GcfEvents/raw_pubsub.json
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
{ | ||
"message": { | ||
"attributes": { "attr1":"value1" }, | ||
"data": "VGV4dCBtZXNzYWdl", | ||
"messageId":"4102184774039362", | ||
"message_id":"4102184774039362", | ||
"orderingKey":"orderxyz", | ||
"publishTime":"2022-02-15T11:28:32.942Z", | ||
"publish_time":"2022-02-15T11:28:32.942Z" | ||
}, | ||
"subscription":"projects/sample-project/subscriptions/sample-subscription" | ||
} |
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like we aren't consistent about what we use here across languages.
//pubsub.googleapis.com/
//pubsub.googleapis.com/UNKNOWN_PUBSUB_TOPIC
Also, I think it is might be possible to always extract the project name from the subscription in the payload.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm. The reason I chose this is to keep structure that will work in the absence of "real" data, but make it obvious that it's not real data. That may or may not be a good choice. Let's discuss this more before actually releasing.
That assumes that the subscription is in the same project as the topic, which may not be the case. (I think cross-project PubSub subscriptions are a thing, with appropriate IAM. I could be wrong.) For the emulator that doesn't matter, but for the genuine PubSub push notifications, I think it's better to give either "obviously wrong" data or "user-specified data" (the URL path) rather than "looks plausible but may be wrong" data.
We should definitely talk about that part more. I'm going to merge this as-is, but file a new issue so that we don't forget about it before the next release.