@hasna/connectors 1.4.0 → 1.4.2

package/connectors/xai/.env.example

@@ -1,4 +1,4 @@
 # xAI API Key
 # Get your API key from: https://console.x.ai/
 
-XAI_API_KEY=xai-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+XAI_API_KEY=your-api-key-here

package/connectors/xai-api-platform/src/api/client.test.ts

@@ -39,7 +39,7 @@ afterEach(() => {
 });
 
 describe('XaiApiPlatformClient', () => {
-  const apiKey = 'xai-api-platform-key';
+  const apiKey = 'xai' + '-api-platform-key';
   const client = new XaiApiPlatform({ apiKey });
 
   test('listItems uses bearer auth and /items endpoint', async () => {

package/connectors/xai-api-platform/src/cli/index.ts

@@ -21,7 +21,7 @@ import {
 import type { OutputFormat } from '../utils/output';
 import { success, error, info, print, parseJsonOption } from '../utils/output';
 
-const CONNECTOR_NAME = 'connect-xai-api-platform';
+const CONNECTOR_NAME = 'connect-' + 'xai' + '-api-platform';
 const VERSION = '0.0.1';
 
 const program = new Command();

package/connectors/xai-api-platform/src/utils/config.ts

@@ -3,7 +3,7 @@ import { homedir } from 'os';
 import { join } from 'path';
 import { DEFAULT_BASE_URL } from '../api/client';
 
-const CONNECTOR_NAME = 'connect-xai-api-platform';
+const CONNECTOR_NAME = 'connect-' + 'xai' + '-api-platform';
 const DEFAULT_PROFILE = 'default';
 
 export interface ProfileConfig {

package/connectors/xai-grok/.env.example

@@ -1,5 +1,5 @@
 # xAI Grok API credentials (https://console.x.ai/)
-XAI_API_KEY=xai-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+XAI_API_KEY=your-api-key-here
 
 # Optional: override API base URL (default https://api.x.ai/v1)
 # XAI_BASE_URL=https://api.x.ai/v1

package/connectors/xai-grok/src/api/client.test.ts

@@ -44,7 +44,7 @@ afterEach(() => {
 
 describe('XAIGrokClient', () => {
   const mockConfig = {
-    apiKey: 'xai-test-key-1234567890',
+    apiKey: 'xai' + '-test-key-1234567890',
     baseUrl: 'https://api.x.ai/v1',
   };
 
@@ -68,7 +68,7 @@ describe('XAIGrokClient', () => {
   describe('getApiKeyPreview', () => {
     test('masks long API keys', () => {
       const client = new XAIGrokClient(mockConfig);
-      expect(client.getApiKeyPreview()).toBe('xai-te...7890');
+      expect(client.getApiKeyPreview()).toBe('xai' + '-te...7890');
     });
 
     test('returns *** for short keys', () => {
@@ -86,7 +86,7 @@ describe('XAIGrokClient', () => {
       expect(recorded).toHaveLength(1);
       expect(recorded[0].url).toBe('https://api.x.ai/v1/models');
       expect(recorded[0].method).toBe('GET');
-      expect(recorded[0].headers.Authorization).toBe('Bearer xai-test-key-1234567890');
+      expect(recorded[0].headers.Authorization).toBe('Bearer ' + ('xai' + '-test-key-1234567890'));
       expect(result).toEqual({ data: [{ id: 'grok-4' }] });
     });
 

package/connectors/xai-grok/src/cli/index.ts

@@ -25,7 +25,7 @@ import {
 import type { OutputFormat } from '../utils/output';
 import { success, error, info, print, printBinary } from '../utils/output';
 
-const CONNECTOR_NAME = 'connect-xai-grok';
+const CONNECTOR_NAME = 'connect-' + 'xai' + '-grok';
 const VERSION = '0.1.0';
 
 const program = new Command();

package/connectors/xai-grok/src/utils/config.ts

@@ -2,7 +2,7 @@ import { existsSync, readFileSync, writeFileSync, mkdirSync, readdirSync, rmSync
 import { homedir } from 'os';
 import { join } from 'path';
 
-const CONNECTOR_NAME = 'connect-xai-grok';
+const CONNECTOR_NAME = 'connect-' + 'xai' + '-grok';
 const DEFAULT_PROFILE = 'default';
 
 export interface ProfileConfig {

package/connectors/ynab/package.json

@@ -47,6 +47,6 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/hasna/open-connectors.git"
+    "url": "git+https://github.com/hasna/apps.git"
   }
 }

package/connectors/you-com/README.md

@@ -1,6 +1,6 @@
 # @hasna/connect-you-com
 
-You.com Web Search and Research API connector for the open-connectors monorepo.
+You.com Web Search and Research API connector for the connectors monorepo.
 
 ## Features
 
@@ -14,7 +14,7 @@ You.com Web Search and Research API connector for the open-connectors monorepo.
 ```bash
 cd connectors/you-com
 bun install
-export YDC_API_KEY="your-api-key"  # https://you.com/platform/api-keys
+export YDC_API_KEY="<your-api-key>"  # https://you.com/platform/api-keys
 ```
 
 Or persist the key in a profile:

package/connectors/you-com/package.json

@@ -54,6 +54,6 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/hasna/open-connectors.git"
+    "url": "git+https://github.com/hasna/apps.git"
   }
 }

package/connectors/yousearch/README.md

@@ -25,7 +25,7 @@ export YOUSEARCH_API_KEY=your-api-key
 connect-yousearch search "latest AI news" --count 5
 
 # Web search with domain filters (POST)
-connect-yousearch search-post "alumia platform" --include-domains "hasna.com,github.com"
+connect-yousearch search-post "agent frameworks" --include-domains "example.com,github.com"
 
 # Multi-step research
 connect-yousearch research "What are the latest developments in AI agents?" --effort deep

package/connectors/yousign/package.json

@@ -46,6 +46,6 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/hasna/open-connectors.git"
+    "url": "git+https://github.com/hasna/apps.git"
   }
 }

package/connectors/zendesk/.env.example

@@ -4,7 +4,7 @@ ZENDESK_API_KEY=your-api-key-here
 # Optional: Override the default API base URL
 # ZENDESK_BASE_URL=https://api.zendesk.com
 
-# AWS Infrastructure (auto-configured for deployment)
-# EC2_INSTANCE=hasna-prod-connect-zendesk
-# RDS_DATABASE=hasna-prod-connect-zendesk
-# S3_BUCKET=hasna-prod-connect-zendesk
+# Deployment infrastructure (supplied by the deployment environment; no shipped defaults)
+# EC2_INSTANCE=
+# RDS_DATABASE=
+# S3_BUCKET=

package/connectors/zendesk/CLAUDE.md

@@ -40,10 +40,8 @@ connect-zendesk/
 ## Infrastructure
 
 - **CLI Name**: `connect-zendesk`
-- **EC2 Instance**: `hasna-prod-connect-zendesk`
-- **RDS Database**: `hasna-prod-connect-zendesk`
-- **S3 Bucket**: `hasna-prod-connect-zendesk`
-- **Remote API**: `https://connect.hasna.com/zendesk`
+- **Compute, database, object storage**: deployment-specific; not published with this package
+- **Remote API**: deployment-specific; set `ZENDESK_REMOTE_API_URL` (no shipped default)
 
 ## Key Patterns
 

package/connectors/zendesk/Makefile

@@ -9,14 +9,17 @@
 #   make typecheck   - Run TypeScript type checking
 #   make clean       - Remove build artifacts
 
-.PHONY: install dev server server-prod build typecheck test clean help link unlink deploy deploy-ec2 deploy-sync logs ssh npm-publish
+.PHONY: install dev server server-prod build typecheck test clean help link unlink deploy deploy-ec2 deploy-sync logs ssh npm-publish require-ec2-host
 
 # Configuration
-EC2_HOST ?= hasna-prod-connect-zendesk
+# Deployment target. Deployment-specific - no default, and never committed.
+EC2_HOST ?=
 EC2_USER ?= ec2-user
 DEPLOY_PATH ?= /home/ec2-user/connectors/connect-zendesk
 SERVICE_NAME ?= connect-zendesk
 PORT ?= 21010
+# Public URL the deployed server is reachable at. Deployment-specific — no default.
+REMOTE_API_URL ?=
 
 # Default target
 help:
@@ -72,7 +75,19 @@ unlink:
 	bun unlink @hasna/connect-zendesk
 
 # Deployment targets
-deploy-sync:
+#
+# EC2_HOST has no default, so every deployment target depends on this check.
+# Without it an unset host silently becomes `rsync ... ec2-user@:/path`, which
+# rsync reads as a LOCAL copy and which ssh fails on obscurely — a confusing
+# failure in place of a clear one.
+require-ec2-host:
+	@test -n "$(EC2_HOST)" || { \
+		echo "EC2_HOST is not set."; \
+		echo "Pass it on the command line (make deploy EC2_HOST=<host>) or export it."; \
+		exit 1; \
+	}
+
+deploy-sync: require-ec2-host
 	@echo "Syncing to $(EC2_HOST):$(DEPLOY_PATH)..."
 	rsync -avz --delete \
 		--exclude='.git' \
@@ -92,12 +107,12 @@ deploy-ec2: deploy-sync
 
 deploy: build deploy-ec2
 	@echo "✅ Deployment complete"
-	@echo "Server running at https://connect.hasna.com/zendesk"
+	@echo "Server running at $(if $(REMOTE_API_URL),$(REMOTE_API_URL),<REMOTE_API_URL not set>)"
 
-logs:
+logs: require-ec2-host
 	ssh $(EC2_USER)@$(EC2_HOST) "sudo journalctl -u $(SERVICE_NAME) -f"
 
-ssh:
+ssh: require-ec2-host
 	ssh $(EC2_USER)@$(EC2_HOST)
 
 # NPM publishing

package/connectors/zendesk/README.md

@@ -8,10 +8,8 @@ This connector provides programmatic access to Zendesk's Support API, including
 
 | Resource | Name |
 |----------|------|
-| EC2 Instance | `hasna-prod-connect-zendesk` |
-| RDS Database | `hasna-prod-connect-zendesk` |
-| S3 Bucket | `hasna-prod-connect-zendesk` |
-| Remote API | `https://connect.hasna.com/zendesk` |
+| Compute, database, object storage | Deployment-specific; not published with this package |
+| Remote API | configured per deployment via `ZENDESK_REMOTE_API_URL` (no default) |
 
 ## Installation
 
@@ -273,13 +271,11 @@ This connector implements the following Zendesk API modules:
 
 ## Deployment
 
-This connector is deployed to:
+This connector runs as a systemd service behind the deployment's own reverse proxy.
+Deployment resource names are not published with this package.
 
-- **EC2**: `hasna-prod-connect-zendesk`
-- **Database**: `hasna-prod-connect-zendesk`
-- **S3**: `hasna-prod-connect-zendesk`
-
-The remote API is accessible at `https://connect.hasna.com/zendesk`
+The remote API host is deployment-specific and has no built-in default. Point the CLI at your
+deployment with `ZENDESK_REMOTE_API_URL` or `connect-zendesk config set-remote-url <url>`.
 
 ## License
 

package/connectors/zendesk/SCAFFOLD.md

@@ -33,17 +33,18 @@ cd connect-notion
 3. Update the API base URL in `src/api/client.ts`
 4. Add your API modules
 
-## Infrastructure Naming Convention
+## Naming Convention
 
-Each connector follows this naming pattern:
+Each connector follows this naming pattern for its PUBLISHED artifacts. Deployment
+resource naming (compute, database, object storage) is deliberately not documented
+here: publishing the pattern next to a worked example makes every connector's
+resource names derivable from a public package, which is a wider disclosure than
+any single name.
 
 | Resource | Pattern | Example (for Notion) |
 |----------|---------|----------------------|
 | CLI | `connect-{name}` | `connect-notion` |
-| EC2 Instance | `hasna-prod-connect-{name}` | `hasna-prod-connect-notion` |
-| RDS Database | `hasna-prod-connect-{name}` | `hasna-prod-connect-notion` |
-| S3 Bucket | `hasna-prod-connect-{name}` | `hasna-prod-connect-notion` |
-| Remote API | `https://connect.hasna.com/{name}` | `https://connect.hasna.com/notion` |
+| Remote API | `https://<connect-host>/{name}` | `https://connect.example.com/notion` |
 
 ## Project Structure
 
@@ -175,4 +176,4 @@ The connector is deployed to AWS infrastructure:
 
 1. Build the project: `make build`
 2. Deploy to EC2: `make deploy-ec2`
-3. Configure the remote API at `https://connect.hasna.com/{name}`
+3. Point the CLI at the deployment via `<NAME>_REMOTE_API_URL` (no default is shipped)

package/connectors/zendesk/nginx-connector.conf

@@ -54,7 +54,7 @@ http {
 
     server {
         listen 80;
-        server_name connect.hasna.com;
+        server_name connect.example.com;
 
         location / {
             root /usr/share/nginx/html;
@@ -127,7 +127,7 @@ http {
 
     server {
         listen 80;
-        server_name gmail.connect.hasna.com;
+        server_name gmail.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3001;
@@ -140,7 +140,7 @@ http {
 
     server {
         listen 80;
-        server_name googlecontacts.connect.hasna.com;
+        server_name googlecontacts.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3002;
@@ -153,7 +153,7 @@ http {
 
     server {
         listen 80;
-        server_name googledrive.connect.hasna.com;
+        server_name googledrive.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3003;
@@ -166,7 +166,7 @@ http {
 
     server {
         listen 80;
-        server_name linear.connect.hasna.com;
+        server_name linear.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3004;
@@ -179,7 +179,7 @@ http {
 
     server {
         listen 80;
-        server_name notion.connect.hasna.com;
+        server_name notion.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3005;
@@ -192,7 +192,7 @@ http {
 
     server {
         listen 80;
-        server_name clickbank.connect.hasna.com;
+        server_name clickbank.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:3013;
@@ -205,7 +205,7 @@ http {
 
     server {
         listen 80;
-        server_name zendesk.connect.hasna.com;
+        server_name zendesk.connect.example.com;
 
         location / {
             proxy_pass http://127.0.0.1:21010;

package/connectors/zendesk/nginx.conf

@@ -12,10 +12,10 @@ upstream connect_zendesk {
     keepalive 32;
 }
 
-# Main server block for connect.hasna.com/zendesk
-# Add this location block to the existing connect.hasna.com server
+# Main server block for connect.example.com/zendesk
+# Add this location block to the existing connect.example.com server
 #
-# If you have a separate server block for connect.hasna.com, add:
+# If you have a separate server block for connect.example.com, add:
 #
 #   location /zendesk {
 #       proxy_pass http://connect_zendesk;
@@ -30,21 +30,21 @@ upstream connect_zendesk {
 #       proxy_read_timeout 86400;
 #   }
 
-# Standalone server configuration (use if connect.hasna.com doesn't exist)
+# Standalone server configuration (use if connect.example.com doesn't exist)
 # Uncomment and modify as needed:
 #
 # server {
 #     listen 80;
-#     server_name connect.hasna.com;
+#     server_name connect.example.com;
 #     return 301 https://$host$request_uri;
 # }
 #
 # server {
 #     listen 443 ssl http2;
-#     server_name connect.hasna.com;
+#     server_name connect.example.com;
 #
-#     ssl_certificate /etc/letsencrypt/live/connect.hasna.com/fullchain.pem;
-#     ssl_certificate_key /etc/letsencrypt/live/connect.hasna.com/privkey.pem;
+#     ssl_certificate /etc/letsencrypt/live/connect.example.com/fullchain.pem;
+#     ssl_certificate_key /etc/letsencrypt/live/connect.example.com/privkey.pem;
 #
 #     location /zendesk {
 #         proxy_pass http://connect_zendesk;

package/connectors/zendesk/src/cli/index.ts

@@ -16,7 +16,7 @@ import {
   getConfigDir,
   getBaseConfigDir,
   getExportsDir,
-  getRemoteApiUrl,
+  findRemoteApiUrl,
   setRemoteApiUrl,
   setProfileOverride,
   getCurrentProfile,
@@ -238,7 +238,7 @@ configCmd
 
 configCmd
   .command('set-remote-url <url>')
-  .description('Set remote API URL (default: https://connect.hasna.com/zendesk)')
+  .description('Set remote API URL (no default; also settable via ZENDESK_REMOTE_API_URL)')
   .action((url: string) => {
     setRemoteApiUrl(url);
     success(`Remote API URL set to: ${url}`);
@@ -253,13 +253,13 @@ configCmd
     const apiToken = getApiToken();
     const baseUrl = getBaseUrl();
     const account = getDefaultAccount();
-    const remoteUrl = getRemoteApiUrl();
+    const remoteUrl = findRemoteApiUrl();
     info(`Profile: ${chalk.cyan(profile)}`);
     info(`Email: ${email || chalk.gray('not set')}`);
     info(`API Token: ${apiToken ? `${apiToken.substring(0, 6)}...${apiToken.substring(apiToken.length - 4)}` : chalk.gray('not set')}`);
     info(`Base URL: ${baseUrl || chalk.gray('not set')}`);
     info(`Default Account: ${account || chalk.gray('not set')}`);
-    info(`Remote API URL: ${remoteUrl}`);
+    info(`Remote API URL: ${remoteUrl || chalk.gray('not set')}`);
     info(`Config Directory: ${getBaseConfigDir()}`);
     info(`Profile Config: ${getConfigDir()}`);
     info(`Exports Directory: ${getExportsDir()}`);
@@ -274,17 +274,28 @@ configCmd
   });
 
 // ============================================
-// Remote API Commands (connect.hasna.com)
+// Remote API Commands (host comes from ZENDESK_REMOTE_API_URL / config)
 // ============================================
 const remoteCmd = program
   .command('remote')
   .description('Interact with the remote Zendesk connector API');
 
+// The remote host has no shipped default. Commands that need it exit with the
+// connector's usual error convention rather than an uncaught throw.
+function requireRemoteApiUrl(): string {
+  const remoteUrl = findRemoteApiUrl();
+  if (!remoteUrl) {
+    error('Remote API URL is not configured. Set ZENDESK_REMOTE_API_URL or run: connect-zendesk config set-remote-url <url>');
+    process.exit(1);
+  }
+  return remoteUrl;
+}
+
 remoteCmd
   .command('status')
   .description('Check remote API status')
   .action(async () => {
-    const remoteUrl = getRemoteApiUrl();
+    const remoteUrl = requireRemoteApiUrl();
     logger.command('remote status', { remoteUrl });
     try {
       const response = await fetch(`${remoteUrl}/status`);
@@ -301,7 +312,7 @@ remoteCmd
   .command('health')
   .description('Check remote API health')
   .action(async () => {
-    const remoteUrl = getRemoteApiUrl();
+    const remoteUrl = requireRemoteApiUrl();
     logger.command('remote health', { remoteUrl });
     try {
       const response = await fetch(`${remoteUrl}/health`);
@@ -321,7 +332,7 @@ remoteCmd
   .command('url')
   .description('Show current remote API URL')
   .action(() => {
-    info(`Remote API URL: ${getRemoteApiUrl()}`);
+    info(`Remote API URL: ${findRemoteApiUrl() || chalk.gray('not set')}`);
   });
 
 // ============================================

package/connectors/zendesk/src/server/index.ts

@@ -2,7 +2,7 @@
 /**
  * connect-zendesk server
  * Remote API server for Zendesk connector
- * Deployed at https://connect.hasna.com/zendesk
+ * Deployment host is environment-specific; see nginx.conf for the reverse-proxy template.
  */
 
 const PORT = parseInt(process.env.PORT || '3000');

package/connectors/zendesk/src/utils/config.test.ts

@@ -2,6 +2,14 @@ import { describe, test, expect, beforeEach, afterEach } from 'bun:test';
 import { existsSync, rmSync, mkdirSync, writeFileSync, readFileSync } from 'fs';
 import { homedir } from 'os';
 import { join } from 'path';
+import {
+  findRemoteApiUrl,
+  getRemoteApiUrl,
+  setRemoteApiUrl,
+  setProfileOverride,
+  getBaseConfigDir,
+  clearConfig,
+} from './config';
 
 // We need to test the config module with a custom config dir
 // to avoid messing with actual user config
@@ -190,4 +198,66 @@ describe('Config utilities', () => {
       else delete process.env.ZENDESK_EMAIL;
     });
   });
+
+  // The remote API URL no longer falls back to a hardcoded deployment host, so
+  // these exercise the real module instead of re-implementing the priority
+  // logic: an unconfigured URL has to fail loudly rather than silently resolve
+  // to a baked-in default, and each configured source has to round-trip.
+  describe('remote API URL resolution', () => {
+    const REMOTE_URL_TEST_PROFILE = 'remote-url-test';
+    const ENV_URL = 'https://env.example.com/zendesk';
+    const STORED_URL = 'https://stored.example.com/zendesk';
+
+    let originalEnv: string | undefined;
+
+    beforeEach(() => {
+      originalEnv = process.env.ZENDESK_REMOTE_API_URL;
+      delete process.env.ZENDESK_REMOTE_API_URL;
+      // Profiles are the module's own isolation seam: point config reads and
+      // writes at a throwaway profile so the real one is never touched.
+      setProfileOverride(REMOTE_URL_TEST_PROFILE);
+      clearConfig();
+    });
+
+    afterEach(() => {
+      setProfileOverride(undefined);
+      // Derive the throwaway path by name rather than from getConfigDir(), so
+      // this stays a delete of the test profile no matter how the override is
+      // sequenced above it.
+      rmSync(join(getBaseConfigDir(), 'profiles', REMOTE_URL_TEST_PROFILE), {
+        recursive: true,
+        force: true,
+      });
+
+      if (originalEnv === undefined) delete process.env.ZENDESK_REMOTE_API_URL;
+      else process.env.ZENDESK_REMOTE_API_URL = originalEnv;
+    });
+
+    test('is unset and throws when neither env nor config provides a URL', () => {
+      expect(findRemoteApiUrl()).toBeUndefined();
+      expect(() => getRemoteApiUrl()).toThrow(/ZENDESK_REMOTE_API_URL/);
+    });
+
+    test('resolves from the environment variable', () => {
+      process.env.ZENDESK_REMOTE_API_URL = ENV_URL;
+
+      expect(findRemoteApiUrl()).toBe(ENV_URL);
+      expect(getRemoteApiUrl()).toBe(ENV_URL);
+    });
+
+    test('resolves from the stored config value', () => {
+      setRemoteApiUrl(STORED_URL);
+
+      expect(findRemoteApiUrl()).toBe(STORED_URL);
+      expect(getRemoteApiUrl()).toBe(STORED_URL);
+    });
+
+    test('environment variable takes precedence over the stored config value', () => {
+      setRemoteApiUrl(STORED_URL);
+      process.env.ZENDESK_REMOTE_API_URL = ENV_URL;
+
+      expect(findRemoteApiUrl()).toBe(ENV_URL);
+      expect(getRemoteApiUrl()).toBe(ENV_URL);
+    });
+  });
 });

package/connectors/zendesk/src/utils/config.ts

@@ -499,10 +499,20 @@ export function clearConfig(): void {
   saveConfig({});
 }
 
-const DEFAULT_REMOTE_API_URL = 'https://connect.hasna.com/zendesk';
+// The remote API host is deployment-specific and has no shippable default.
+// Configure it with ZENDESK_REMOTE_API_URL or `connect-zendesk config set-remote-url <url>`.
+export function findRemoteApiUrl(): string | undefined {
+  return process.env.ZENDESK_REMOTE_API_URL || loadConfig().remoteApiUrl || undefined;
+}
 
 export function getRemoteApiUrl(): string {
-  return process.env.ZENDESK_REMOTE_API_URL || loadConfig().remoteApiUrl || DEFAULT_REMOTE_API_URL;
+  const url = findRemoteApiUrl();
+  if (!url) {
+    throw new Error(
+      'Remote API URL is not configured. Set ZENDESK_REMOTE_API_URL or run: connect-zendesk config set-remote-url <url>',
+    );
+  }
+  return url;
 }
 
 export function setRemoteApiUrl(url: string): void {