fix(deploy): cover integration connect preflight#110
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds an optional --no-prompt path: ConnectAllInput gains noPrompt, connectIntegrations aborts early (records a failed outcome or throws for subscription flows) when a provider is not connected and noPrompt is set; deploy forwards the flag and tests validate behaviors. Changesno-prompt integration connection fail-fast
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🔴 noPrompt flag not checked in subscription section, allowing interactive prompt despite --no-prompt
When noPrompt is true but all declared integrations are already connected, the integration loop completes normally and execution falls through to the subscription check (line 250). The subscription section at line 259-264 only gates on input.noConnect, not input.noPrompt. If the subscription is not connected, input.io.confirm(...) is called at line 265, prompting the user interactively — directly contradicting the --no-prompt flag whose documented purpose is "Fail instead of prompting for cloud auth/integration setup" (packages/deploy/src/types.ts:24-25). In a CI/non-interactive environment this would block waiting on stdin.
(Refers to lines 259-264)
Was this helpful? React with 👍 or 👎 to provide feedback.
Resolve the connect.ts conflict with the integration auth fail-fast changes and make subscription provider setup honor --no-prompt without prompting.
Follow-up to merged workforce#109 review feedback.\n\nWhat changed:\n- Added deploy-loop coverage for missing github+notion integrations where both connect successfully and deploy proceeds.\n- Added deploy-loop coverage where one integration connect fails and deploy aborts before launch.\n- Wired --no-prompt into the integration preflight path so missing integrations fail immediately with clear guidance and without opening a connect flow.\n\nVerification:\n- corepack pnpm --filter @agentworkforce/deploy test