fix(google-chat): allow HTTP inbound without Pub/Sub (#36035 salvage) - #65545
Merged
Conversation
alt-glitch
added
type/feature
teknium1
force-pushed
the
salvage/36035-gchat-http-inbound
branch
from
July 16, 2026 11:49
0675314 to
f6f9570
Compare
This was referenced Jul 16, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Google Chat inbound no longer requires Pub/Sub:
GOOGLE_CHAT_HTTP_EVENTS_URLadds a direct HTTP events transport as an alternative, making Pub/Sub optional.Salvage of #36035 by @aeyeopsdev (root of their Google Chat stack) — clean cherry-pick onto current main, authorship preserved. Fully contained in the plugin:
plugins/platforms/google_chat/{adapter.py,plugin.yaml}+ its test file.Changes
plugins/platforms/google_chat/adapter.py: HTTP events inbound path alongside the existing Pub/Sub transport.plugins/platforms/google_chat/plugin.yaml: config surface for the new URL.tests/gateway/test_google_chat.py: +49 lines of transport tests.scripts/release.py: AUTHOR_MAP entry for aeyeopsdev.Validation
scripts/run_tests.sh tests/gateway/test_google_chat.py→ 164 passed.Stack note: #36068 (clarify cards) is independent and shipped separately; #36061/#36069 (generic gateway HTTP callback route + card clicks) remain open pending this landing and a rebase on their side.
Infographic