langchain-ai/helm
1
0
Fork 0
mirror of https://github.com/langchain-ai/helm.git synced 2026-07-25 13:06:17 -04:00
Code Issues 24 Packages Projects Releases 10 Wiki Activity

[PR #672] [MERGED] fix: add missing microsoftOAuthProvider mapping #672

New Issue
Closed
opened 2026-06-05 19:17:21 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 19:17:21 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/helm/pull/672
Author: @saad-supports-langchain
Created: 4/9/2026
Status: ✅ Merged
Merged: 4/9/2026
Merged by: @saad-supports-langchain

Base: main ← Head: fix/add-microsoft-oauth-provider-helm

📝 Commits (2)

  • bbd1077 fix: add missing microsoftOAuthProvider mapping to Helm chart
  • bdc2a55 chore: bump image versions to 0.13.41

📊 Changes

4 files changed (+32 additions, -25 deletions)

View changed files

📝 charts/langsmith/Chart.yaml (+2 -2)
📝 charts/langsmith/README.md (+13 -12)
📝 charts/langsmith/templates/_helpers.tpl (+4 -0)
📝 charts/langsmith/values.yaml (+13 -11)

📄 Description

Summary

  • Adds microsoftOAuthProvider to values.yaml under config.agentBuilder.oauth
  • Adds MICROSOFT_OAUTH_PROVIDER env var mapping in agentBuilderOAuthEnvVars template
  • Follows the same pattern as the existing five providers (Google, Slack, LinkedIn, Linear, GitHub)

Without this, self-hosted customers who set microsoftOAuthProvider in their Helm values get no effect — the value is silently ignored, and all Outlook/Teams/SharePoint/365 Docs tools are disabled on the tool server. The trigger server also skips the Outlook cron trigger.

Test plan

  • helm template dry-run with microsoftOAuthProvider set — MICROSOFT_OAUTH_PROVIDER appears on tool-server, trigger-server, and host-backend deployments
  • helm template dry-run with microsoftOAuthProvider empty — env var absent (no change to default behavior)
  • Deployed to self-hosted EKS cluster — tool server logs confirm microsoft_tools_enabled (19 tools), microsoft_sharepoint_tools_enabled (19), microsoft_document_tools_enabled (17)
  • Trigger server logs confirm outlook_trigger_enabled with provider: "microsoft"
  • Reverted to remote chart 0.13.39 — confirmed Outlook tools are absent without this fix

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/helm/pull/672 **Author:** [@saad-supports-langchain](https://github.com/saad-supports-langchain) **Created:** 4/9/2026 **Status:** ✅ Merged **Merged:** 4/9/2026 **Merged by:** [@saad-supports-langchain](https://github.com/saad-supports-langchain) **Base:** `main` ← **Head:** `fix/add-microsoft-oauth-provider-helm` --- ### 📝 Commits (2) - [`bbd1077`](https://github.com/langchain-ai/helm/commit/bbd1077a46fab34ba323656cb74249c5cc36746f) fix: add missing microsoftOAuthProvider mapping to Helm chart - [`bdc2a55`](https://github.com/langchain-ai/helm/commit/bdc2a550190fb8974dfdd6132e96f4c26a487112) chore: bump image versions to 0.13.41 ### 📊 Changes **4 files changed** (+32 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `charts/langsmith/Chart.yaml` (+2 -2) 📝 `charts/langsmith/README.md` (+13 -12) 📝 `charts/langsmith/templates/_helpers.tpl` (+4 -0) 📝 `charts/langsmith/values.yaml` (+13 -11) </details> ### 📄 Description ## Summary - Adds `microsoftOAuthProvider` to `values.yaml` under `config.agentBuilder.oauth` - Adds `MICROSOFT_OAUTH_PROVIDER` env var mapping in `agentBuilderOAuthEnvVars` template - Follows the same pattern as the existing five providers (Google, Slack, LinkedIn, Linear, GitHub) Without this, self-hosted customers who set `microsoftOAuthProvider` in their Helm values get no effect — the value is silently ignored, and all Outlook/Teams/SharePoint/365 Docs tools are disabled on the tool server. The trigger server also skips the Outlook cron trigger. ## Test plan - [x] `helm template` dry-run with `microsoftOAuthProvider` set — `MICROSOFT_OAUTH_PROVIDER` appears on tool-server, trigger-server, and host-backend deployments - [x] `helm template` dry-run with `microsoftOAuthProvider` empty — env var absent (no change to default behavior) - [x] Deployed to self-hosted EKS cluster — tool server logs confirm `microsoft_tools_enabled` (19 tools), `microsoft_sharepoint_tools_enabled` (19), `microsoft_document_tools_enabled` (17) - [x] Trigger server logs confirm `outlook_trigger_enabled` with `provider: "microsoft"` - [x] Reverted to remote chart 0.13.39 — confirmed Outlook tools are absent without this fix 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 19:17:21 -04:00
yindo closed this issue 2026-06-05 19:17:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/helm#672
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?