Skip to content
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

Add Google Chat webhook exposed key handling #606

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gjcthinkst
Copy link
Contributor

Proposed changes

Add Google Chat webhook support for exposed API key alerts. While we're in the area also do some refactoring and general improvements for the Google Chat webhook.

Types of changes

What types of changes does your code introduce to this repository?

  • New feature (non-breaking change which adds functionality)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Lint and unit tests pass locally with my changes (if applicable)
  • I have run pre-commit (pre-commit in the repo)
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Linked to the relevant github issue or github discussion

Further comments

I tested the changes to the Google Chat webhook by creating a new AWS API key token, triggering it normally and manually creating an exposed key alert with CURL (with 25 Dec as the exposed time) and checked that all three Google chat messages displayed correctly.

CleanShot 2024-11-08 at 15 45 59@2x

An example of the current (before this change) Google Chat message format is shown below.

CleanShot 2024-11-07 at 15 55 55@2x

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