feat(connectors): add connectors to deploy command

[Paveltarno]

Note

Description

This PR refactors the OAuth authorization prompt logic into a reusable module and enhances connector deployment messaging. The new oauth-prompt.ts module provides generic OAuth flow utilities that are shared between connectors push and deploy commands. The refactoring improves the user experience by providing clearer messages about pending OAuth authorizations and offering multiple ways to complete authorization (re-run command or manually open links).

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• Created src/cli/commands/connectors/oauth-prompt.ts module with reusable OAuth flow utilities:
  • filterPendingOAuth() - Type-safe filtering of connector results that need OAuth
  • promptOAuthFlows() - Interactive OAuth authorization prompts with skipPrompt option
  • PendingOAuthResult type for type-safe OAuth handling
• Refactored src/cli/commands/connectors/push.ts to use the new OAuth prompt module:
  • Simplified OAuth handling by delegating to promptOAuthFlows()
  • Passes skipPrompt: true when process.env.CI is detected
  • Updated skip messages to mention manual link authorization
• Updated src/cli/commands/project/deploy.ts to handle connector OAuth flows:
  • Calls promptOAuthFlows() after deployment when connectors need authorization
  • Respects -y flag and CI environment to skip interactive prompts
  • Displays helpful message with authorization instructions when OAuth is skipped
• Enhanced src/core/project/deploy.ts:
  • Returns connectorResults in DeployAllResult interface for OAuth handling
• Added test coverage in tests/cli/deploy.spec.ts:
  • Test for connectors in deploy command with OAuth already authorized
  • Test for connectors needing OAuth with -y flag (verifies skip message)
  • Updated all existing deploy tests to mock connectorsList endpoint

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (bun test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated AGENTS.md if I made architectural changes

Additional Notes

This PR builds on the connector infrastructure added in the target branch (pavelta-connectors-1). Key design decisions:

• Environment-agnostic helper: The oauth-prompt module doesn't check process.env.CI directly. Instead, callers pass skipPrompt: true based on their context, making the helper more testable and reusable across different commands.
• Improved user messaging: When OAuth is skipped (via -y flag or CI environment), users now see clearer messages with both the authorization URLs and instructions for multiple authorization methods (re-run command or manually open links).
• Type safety: Uses type guards (filterPendingOAuth) to ensure type-safe handling of OAuth results throughout the flow.

---

_{🤖 Generated by Claude | 2026-02-11 20:15 UTC}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.0.30-pr.211.475080d

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.0.30-pr.211.475080d"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.0.30-pr.211.475080d"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.0.30-pr.211.475080d
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[claude]

Code Review

Found 1 issue that needs attention:

Missing API mock in test

File: tests/cli/deploy.spec.ts
Lines: 124-137 (new test "deploys connectors successfully with -y flag")
Issue: Missing mockConnectorSet() calls for the 3 connectors in the test fixture

When deployAll() calls connectorResource.push(connectors), it executes pushConnectors() which calls setConnector() for each connector. Without mocking these API calls, the test will fail because MSW doesn't have a handler for the unmocked requests.

Fix: Add mockConnectorSet() call after line 130 (after mockConnectorsList) and before the t.run() call:

t.api.mockConnectorSet({
  redirect_url: null,
  connection_id: null,
  already_authorized: true,
});

See:

cli/tests/cli/connectors_push.spec.ts

Lines 31 to 35 in 68ece4e

	connection_id: null,
	already_authorized: true,
	});
	const result = await t.run("connectors", "push");

---

All other changes look good:

• ✅ Import statement follows existing patterns
• ✅ Resource integration matches entity/function/agent patterns
• ✅ Test fixture exists with correct data (3 connectors)
• ✅ AGENTS.md update is appropriate

[claude]

Code review

Found 1 issue that needs attention:

Unused variable in OAuth handling (src/cli/commands/project/deploy.ts:98)
The variable pending is assigned but never used in the log message on lines 99-101. Users won't be informed which connectors need authorization.

Compare with the analogous code in src/cli/commands/connectors/push.ts lines 91-96 where pending is correctly interpolated into the message to show users which connectors are pending (e.g., "Pending: google_calendar, slack").

Suggested fix:
Change line 99-101 from:

log.info(
  `To authorize, run 'base44 connectors push' or open the links above in your browser.`
);

To:

log.info(
  `Pending: ${pending}. To authorize, run 'base44 connectors push' or open the links above in your browser.`
);

This will provide users with actionable information about which specific connectors require their attention.

---

Checked for bugs and CLAUDE.md compliance. All other changes follow the established patterns correctly.

[Paveltarno]

Re: comment

Fixed in f4d2ac1 - Added mockConnectorSet() to the deploy connector test.