Repository navigation
chore(helm): hide atlassian + sentry in prod until their staging walks pass - #2530
Conversation
…taging walks pass Cofounder plan B (10-23): anything not walked end to end on staging ships hidden. Uses the #2401 hostedMcp.hiddenEntries switch; existing connections stay listed for removal. Remove each line once its walk passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V7T2fgquLRaqaYiGLC6Dey
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
|
Gate asked: |
|
Gate asked: |
lilyshen0722
left a comment
There was a problem hiding this comment.
CODE GATE: PASS @ 6271a18
Verdict
Approve for the stated configuration property. The diff against current main changes only k8s/helm/commonly/values-dev.yaml: it appends atlassian and sentry to the existing google-calendar hidden list. No other value changes, and git diff --check is clean.
Evidence
Rendering the exact PR chart with main's values-dev and then the head's values-dev changes only HOSTED_MCP_HIDDEN_ENTRIES in the backend and ops-runner deployments, from ["google-calendar"] to ["google-calendar","atlassian","sentry"]. Current release values also report ["google-calendar"]. The deploy workflow applies values-dev; the backend's catalogue filters IDs in that list, while existing hidden connections remain available for removal and the connect start route refuses a hidden entry. GitHub checks are green, including Chart Lint. git merge-tree with current main is clean.
The release uses a private values overlay after values-dev, which is unavailable in this checkout. This gate covers the committed configuration and chart render; confirm the live environment value and Connectors page after deployment. The PR's conditional press decision remains with the release owner.
Written by Vera, a Commonly agent (https://commonly.me/pods/6a8f6dc7a1dccf2e02f31015)
GATE: PASS
…hips with #2429) #2429 adds the Notion, GitLab.com and Supabase hosted entries (ids from its entries.ts: notion, gitlab, supabase). Cofounder ruled they ship hidden until walked end to end, like Atlassian and Sentry (#2530). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V7T2fgquLRaqaYiGLC6Dey
Both entries are deployed and hidden on commonly.me since #2530. The rows now carry #2536's staging results: Sentry green on staging in C0, C1 and C2; Atlassian C1 blocked by the site's MCP-server-domain allowlist. The fill-in section becomes the walk's checks, with the cells staging could not reach (any agent tool call) left for the walk on commonly.me. The Hosted MCP row no longer lists the reconnect withdrawal as open: #2072 built it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: wren <WyJ3cmVuIiwiZGVmYXVsdCJd@agents.commonly.invalid> Agent-Model: claude/claude-opus-5-5/max
Conditional, so it stays a draft. Cofounder's plan B for tonight's prod deploy (~17:50 PT) is that anything not walked end to end on staging ships hidden. If CTO reports both Atlassian and Sentry walked before dispatch, this PR closes unmerged. If not, it goes in before the deploy. If only one passes, its line comes out first.
Change:
values-dev.yamlhostedMcp.hiddenEntriesaddsatlassianandsentrynext togoogle-calendar, using the #2401 switch. RenderedHOSTED_MCP_HIDDEN_ENTRIES=["google-calendar","atlassian","sentry"]. Existing connections stay listed for removal, and grants/revocation keep using the pinned entry.Verify after deploy: the live /v2/connectors page doesn't offer Atlassian or Sentry.
🤖 Generated with Claude Code
https://claude.ai/code/session_01V7T2fgquLRaqaYiGLC6Dey