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

feat(cloud-function): migrate to @sentry/google-cloud-serverless #11230

Merged

Conversation

caugner
Copy link
Contributor

@caugner caugner commented May 31, 2024

Summary

(MP-1168)

Problem

The Sentry integration with our Cloud Function using @sentry/serverless doesn't seem to work, as we didn't notice the BSA errors.

Solution

Migrate to @sentry/google-cloud-serverless.


How did you test this change?

Deployed to stage since 2024-06-05.

@caugner caugner marked this pull request as ready for review June 6, 2024 12:09
@caugner caugner requested a review from a team as a code owner June 6, 2024 12:09
@github-actions github-actions bot added the merge conflicts 🚧 Please rebase onto or merge the latest main. label Jun 24, 2024
Copy link
Contributor

This pull request has merge conflicts that must be resolved before it can be merged.

@github-actions github-actions bot added the idle label Jul 24, 2024
@github-actions github-actions bot removed the merge conflicts 🚧 Please rebase onto or merge the latest main. label Aug 7, 2024
Copy link
Contributor

@argl argl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still a thing? I brought it up to main, looks good so far.

@github-actions github-actions bot removed the idle label Aug 7, 2024
@caugner caugner merged commit 872111a into main Aug 9, 2024
13 checks passed
@caugner caugner deleted the MP-1168-migrate-cloud-function-to-sentry-google-cloud-serverless branch August 9, 2024 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants