feat: msft teams support for critical alerts

[alpetric]

Important

Adds Microsoft Teams support for critical alerts, including backend API endpoints, database migrations, and frontend UI components for configuration.

• Behavior:
  • Adds support for Microsoft Teams in critical alerts, allowing configuration of Teams channels for alert notifications.
  • Introduces new API endpoint /teams/sync in openapi.yaml for synchronizing Teams information.
• Database:
  • Adds new SQL queries for handling Teams settings in .sqlx/query-*.json files.
  • Adds migration scripts 20250115223046_teams_global_settings.up.sql and 20250115223046_teams_global_settings.down.sql for Teams settings.
• Backend:
  • Updates main.rs to handle Teams settings changes.
  • Adds teams_ee.rs for Teams service routing.
  • Modifies oauth2_ee.rs to include Teams in OAuth client building.
• Frontend:
  • Updates AuthSettings.svelte, InstanceSetting.svelte, and OAuthSetting.svelte to include Teams in OAuth settings.
  • Modifies InstanceSettings.svelte to handle Teams in critical alert channels.
  • Updates IconedResourceType.svelte to include Teams icon.

^{This description was created by for 5738fdb. It will automatically update as commits are pushed.}

[cloudflare-workers-and-pages]

Deploying windmill with    Cloudflare Pages

Latest commit:	5738fdb
Status:	✅  Deploy successful!
Preview URL:	https://b0ce2d6e.windmill.pages.dev
Branch Preview URL:	https://alp-msft-teams.windmill.pages.dev

View logs

[alpetric]

needs ee merge first for ee_full to pass

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 5738fdb in 1 minute and 20 seconds

More details

• Looked at 836 lines of code in 29 files
• Skipped 0 files when reviewing.
• Skipped posting 7 drafted comments based on config settings.

1. backend/migrations/20250115223046_teams_global_settings.down.sql:1

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

2. backend/migrations/20250115223046_teams_global_settings.up.sql:1

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

3. backend/windmill-api/src/teams_ee.rs:5

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

4. backend/.sqlx/query-08dd2ea6b17a52bce352d6443d7d009cfc9da0d3b2bd1f40d422b550779e5324.json:20

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

5. backend/.sqlx/query-44a12919fb154055f1142cc078ef131f8a0c9cdb37cfba6283a6718480b02a4b.json:34

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

6. backend/.sqlx/query-84d048ea323758842dc564c700b524d1a5b196a7b77afcb02f46b84b22088bbf.json:20

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

7. backend/.sqlx/query-9c72b2962d0919353cfe5af710e857d432dff44e343b8f0610208d42ff5afd14.json:14

• Draft comment:
  Add a newline at the end of the file for better POSIX compliance.
• Reason this comment was not posted:
  Confidence changes required: 10%
  The code is missing a newline at the end of the file, which is a common best practice for POSIX compliance and to avoid potential issues with some tools.

Workflow ID: wflow_cNikAoiU3TkuHtSo

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.