Skip to content

chore(seer-infra-telemetry): Set up temporary code to provide Seer with GCP integration internally…#120106

Merged
shashjar merged 1 commit into
masterfrom
shashjar/temporary-code-to-provide-gcp-connection-internally-in-sentry-org
Jul 20, 2026
Merged

chore(seer-infra-telemetry): Set up temporary code to provide Seer with GCP integration internally…#120106
shashjar merged 1 commit into
masterfrom
shashjar/temporary-code-to-provide-gcp-connection-internally-in-sentry-org

Conversation

@shashjar

Copy link
Copy Markdown
Member

Setting up some temporary code to provide the GCP provider connection to Seer only internally for the Sentry org.

Only for the short-term to allow for dogfooding internally, will be torn down in favor of the proper approach.

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 20, 2026
@shashjar
shashjar requested a review from wedamija July 20, 2026 18:26
@linear-code

linear-code Bot commented Jul 20, 2026

Copy link
Copy Markdown

CW-1683

@shashjar
shashjar marked this pull request as ready for review July 20, 2026 18:26
@shashjar
shashjar requested a review from a team as a code owner July 20, 2026 18:26

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 3e7d609. Configure here.

Comment thread src/sentry/seer/agent/monitoring_providers.py
Comment thread src/sentry/seer/agent/monitoring_providers.py
Comment thread src/sentry/seer/agent/monitoring_providers.py
Comment on lines +182 to +184
# TEMPORARY: hardcoded GCP MCP connections for the Sentry org (id=1) for internal dogfooding.
# Remove when the full GcpIntegrationProvider + setup UI is built.
if organization.id == 1:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wonder if it'd be better to use a feature flag instead of hardcoding, even though it's temporary?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

hmm we just want to uniquely identify the sentry org to make sure this logic can never be extended to any other org, so i think i'd prefer hardcoding the org. thoughts?

@shashjar
shashjar merged commit 5127661 into master Jul 20, 2026
68 checks passed
@shashjar
shashjar deleted the shashjar/temporary-code-to-provide-gcp-connection-internally-in-sentry-org branch July 20, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants