Manage non-SCM integrations from the CLI #1520

Broader scope of #1519: driving Slack, Linear, Jira, PagerDuty, Discord, MS Teams, etc. from the CLI.

Existing APIs

• Native providers (Slack, Jira, PagerDuty, Discord, MS Teams, Opsgenie, …) use the same API pipeline as Add SCM integrations from the CLI #1519.
• No-config providers: POST /api/0/organizations/{org}/integrations/direct-enable/{provider}/ (source).
• Sentry Apps: POST /api/0/organizations/{org}/sentry-app-installations/ with slug.
• List available: GET /config/integrations/; list installed: GET /integrations/; remove: DELETE /integrations/{id}/.

Limitations / edge cases

• All pipeline limitations from Add SCM integrations from the CLI #1519 apply (session-bound state, browser OAuth relay).
• Slack's OAuth step also requests user scopes, so a user must authorize in a browser.
• Direct-enable is PRIVATE, only works for providers marked directEnable, and returns 400 if a single-install provider is already enabled.
• Linear looks like a Sentry App rather than a native provider (unverified); Sentry App installs follow a different flow and permissions than native integrations.
• Feature-flagged providers return 404.

via @sergical.

--

View Junior Session [Sentry]