Merge branch 'master' into mz/unleash-docs

Author: cmanallen

apps/changelog/package.json

@@ -26,7 +26,7 @@
     "@radix-ui/themes": "^3.1.3",
     "@sentry/nextjs": "8.36.0",
     "@spotlightjs/spotlight": "^2.1.1",
-    "next": "15.0.3",
+    "next": "15.1.2",
     "next-auth": "^4.24.5",
     "next-mdx-remote": "^4.4.1",
     "nextjs-toploader": "^1.6.6",

develop-docs/integrations/azuredevops.mdx

@@ -0,0 +1,75 @@
+---
+title: Azure DevOps Integration
+sidebar_title: Azure DevOps
+---
+
+## Create an Azure Application
+
+Log into your Azure DevOps account or create a new one, and ensure you have a project set up.
+
+Make sure the organization has third-party access via OAuth enabled in the organization settings.
+![3p-oauth](./3p-oauth.png)
+
+
+To use the Azure DevOps integration you'll need to create an application.
+
+To start, you will need access to a [Microsoft Entra Admin Portal](https://entra.microsoft.com/#home)
+
+![Register App](./register-app.png)
+
+
+When configuring the app, use the following values:
+
+| Setting                         | Value                                                                                              |
+| ------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Supported account types         | Accounts in any organizational directory |
+| Redirect URI                    | `{YOUR_DOMAIN}/extensions/vsts/setup`                                                              |
+
+<Note>
+
+Take note of your App ID as we'll need it later.
+![App ID](./app-id.png)
+
+</Note>
+
+Next go to Manager -> API Permissions to add the following permissions:
+* Azure DevOps (`vso.code`, `vso.graph`, `vso.work_item`, `vso.service_endpoint`)
+* Microsoft Graph (`User.Read`) (This should be added by default)
+
+![Permissions](./perms.png)
+
+Go to the "Certificates & secrets" tab and create a new client secret. Make sure you copy the secret as we'll need it later.
+
+![Client Secret](./client-secret.png)
+
+Add the App ID and Client Secret to `devlocal.py` like this:
+
+```python
+# Azure DevOps #
+SENTRY_OPTIONS["vsts_new.client-id"] = your-app-id
+SENTRY_OPTIONS["vsts_new.client-secret"] = your-client-secret
+```
+
+You can also add the App ID and Client Secret to `config.yml` like this:
+
+```yml
+# Azure DevOps #
+vsts_new.client-id: your-app-id
+vsts_new.client-secret: your-client-secret
+```
+
+You will also need to enable the feature flag to use the new Azure DevOps integration.
+Enable the `migrate-azure-devops-integration` feature flag in your organization.
+Add the following to your `devlocal.py` file:
+
+```python
+SENTRY_FEATURES["organizations:migrate-azure-devops-integration"] = True
+```
+
+<Alert title="Feature Flag" level="info">
+
+This is a temporary measure until we fully migrate to the new Azure DevOps integration and remove references to the old one.
+
+</Alert>
+
+Follow our [documentation on installing and configuring the Azure DevOps integration](https://docs.sentry.io/organization/integrations/source-code-mgmt/azure-devops/) to finish installation and use the integration.

develop-docs/integrations/azuredevops/3p-oauth.png

@@ -28,7 +28,7 @@ discord.client-secret: "<client secret>"
 discord.bot-token: "<bot token>"
 ```
 
-**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok and add `system.url-prefix: "https://<your_subdomain>.ngrok.io"` to your `~/.sentry/config.yml`. Otherwise, installing the Discord bot won't work, as it will not be able to communicate with your local Sentry instance.
+**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok to expose your local Sentry instance to the internet. Otherwise, the OAuth2 Redirect URI will not work.
 
 After you update the <code>config.yml</code>, restart your Sentry server to continue the setup process.
 

develop-docs/integrations/azuredevops/app-id.png

@@ -13,19 +13,21 @@ After naming your app and connecting your workspace, navigate to __Basic Informa
 
 Here’s where you’ll connect your self-hosted Sentry instance to your newly created Slack app.
 
-Copy your Client ID, Client Secret, and Signing Secret and paste them into <code>config.yml</code>.
+Copy your Client ID, Client Secret, and Signing Secret and paste them into `~/.sentry/config.yml` or `~/.sentry/sentry.conf.py`.
 
 ```yaml
 slack.client-id: <client id>
 slack.client-secret: <client secret>
 slack.signing-secret: <signing secret>
 ```
 
-**NOTE**: If you're doing local Sentry development, you should use a tool like Ngrok and add `system.url-prefix: "https://<your_subdomain>.ngrok.io"` to your `~/.sentry/config.yml`, otherwise, installing the Slack APP will complain because the redirect URI points to `localhost:8000`. Also, install the Slack integration from the ngrok subdomain or it will fail to install.
+If you're a Sentry employee, you can set the `slack.client-id` and `slack.client-secret` in `devlocal.py` inside `getsentry` instead.
 
-After you update the <code>config.yml</code> you need to restart your Sentry server to continue configuring the Slack app.
+**NOTE**: If you're doing local Sentry development, you should usse ngrok and install the Slack integration from the ngrok subdomain or it will fail to install. Refer to [Developing with Ngrok](https://develop.sentry.dev/development-infrastructure/ngrok/) for more information.
 
-<Alert title="Note" level="info">
+After you update the `config.yml`, `sentry.conf.py`, or `devlocal.py` you need to restart your Sentry server to continue configuring the Slack app.
+
+<Alert title="Note (for self-hosted users)" level="info">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
@@ -112,8 +114,13 @@ Navigate to __Slash Commands__ under __Features__. Click __Create New Command__
 
 | Setting                         | Value                                         |
 | ------------------------------- | --------------------------------------------- |
-| Command                         | `/sentry`                                     |
-| Request URL                     | `{YOUR_DOMAIN}/extensions/slack/commands/` |
+| Command                         | `/{yourname}-sentry`                          |
+| Request URL                     | `{YOUR_DOMAIN}/extensions/slack/commands/`    |
+
+
+<Alert title="Note" level="info">
+    When creating the slash command, don’t use `/sentry`. Do something like `/{your_name}-sentry`. If multiple apps are installed with the same slash command, the most recently installed one takes over.
+</Alert>
 
 At the bottom of the page, click __Save__.