Skip to content

Add multi-channel approver support to Google Chat App setup - #2341

Open
sshrushanth-ks wants to merge 4 commits into
gchat-add-multi-channel-approver-supportfrom
gchat-add-multi-channel-approver-support-int
Open

Add multi-channel approver support to Google Chat App setup#2341
sshrushanth-ks wants to merge 4 commits into
gchat-add-multi-channel-approver-supportfrom
gchat-add-multi-channel-approver-support-int

Conversation

@sshrushanth-ks

@sshrushanth-ks sshrushanth-ks commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Multi-channel approver support was added to Google Chat setup, providing feature parity with Slack.

Changes

  • gchat_app_setup.py: Removed standalone approvals space prompt. Replaced _is_valid_space_id() with _validate_gchat_space_id() with stricter validation. Removed duplicate FIELD_APPROVALS_SPACE_ID from record fields. Replaced unsafe assert with explicit CommandError raising. Added CommandError import.
  • models.py: Made approvals field REQUIRED (no default). Added @property chat_approvals_space_id delegating to approvals.single_channel_id. Removed duplicate constants from GChatConstants.
  • test_gchat_app_setup.py: Updated tests to use ApprovalsConfig. Added test_chat_approvals_space_id_property() to verify invariant. Added test_multi_channel_approval_config_serialization() for multi-team coverage.
  • test_docker_setup_ownership.py: Added 3 GChat security ownership tests (folder/record squatting prevention).

@sshrushanth-ks sshrushanth-ks self-assigned this Sep 2, 2026
-Remove duplicate FIELD_APPROVALS_SPACE_ID from record fields
-Fix type annotation: any → object in _validate_service_account_dict()
-Replace unsafe assert with proper CommandError error handling
-Add test_multi_channel_approval_config_serialization() for multi-team coverage
-Change default channel field to chat_approvals_space_id (from approvals_channel_id)
-Use space_id instead of channel_id in approvals_teams JSON for teams
-Create _gchat_approvals_record_fields() for GChat-specific serialization
-Update tests to verify new field naming conventions
@sshrushanth-ks
sshrushanth-ks marked this pull request as ready for review September 2, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants