Repository navigation
feat(cli): add integration list and delete commands - #1523
Merged
Merged
Conversation
Add `sentry integration list` (alias `sentry integrations`) and `sentry integration delete` for integrations installed on an organization. List sends includeConfig=0 so Sentry skips the slow third-party config fetch. Delete explains the missing org:integrations scope on 403, since the default login does not request it. Refs #1519, #1520 Co-Authored-By: Burak Yigit Kaya <burak.kaya@sentry.io> Co-Authored-By: Miguel Betegon <miguel.betegon@sentry.io> Co-Authored-By: Sergiy Deceive-skiy <sergiy.dybskiy@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
…egration delete Add org:integrations to the default OAuth scopes (no admin scopes). integration delete now checks the stored grant before confirming and, for older logins, explains it needs elevated permissions and re-runs authorization itself instead of telling the user which command to run. A 403 after that explains the org role requirement. Co-Authored-By: Burak Yigit Kaya <burak.kaya@sentry.io>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6e5dc3d. Configure here.
…on delete Unattended runs must never block on the device flow, so elevation stays interactive-only. The 403 detail and docs now say re-authorization is skipped with --yes or --json instead of blaming a missing terminal.
BYK
approved these changes
Oct 16, 2026
Examples now live in docs.examples, so --help, the generated docs, and the skill references render them from one place. The fragment keeps only the permissions note. AGENTS.md now points examples at docs.examples and fixes the stale fragment paths.
This branch was previously deployed
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
1 participant
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.
First step toward managing integrations from the CLI (#1519, #1520):
sentry integration list(aliassentry integrations) andsentry integration delete [<org>/]<integration-id>(aliasesremove,rm).listuses the shared org-list framework (auto-detect,<org>/pagination,--json). It sendsincludeConfig=0: Sentry fetches third-party config for any other value, includingfalse, which can add seconds per request. The list includes disabled and pending-deletion installs, so the table shows the per-org status.deletechecks the integration exists, then supports--dry-run/--yesand type-to-confirm like the other delete commands.org:integrationsis now one of the default OAuth scopes (no admin scopes added; read-only logins still exclude it). Sentry requires it to uninstall an integration.deletechecks the stored grant before the confirmation prompt, says the action needs elevated permissions, and re-runs authorization itself (newensureScopesForActioninscope-recovery.ts), so the user isn't told to run a command. Without a TTY it can't prompt, so a 403 explains the stale login; a 403 after elevation explains the owner/manager role requirement.Installing integrations isn't included; Sentry's install pipeline is tied to the browser session today (see #1519 and getsentry/sentry#127853).
via byk.
--
View Junior Session [Sentry]