@hasna/connectors 1.4.1 → 1.4.2

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/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,9 +40,7 @@ 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`
+- **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,10 +9,11 @@
 #   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
@@ -74,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' \
@@ -96,10 +109,10 @@ deploy: build deploy-ec2
 	@echo "✅ Deployment complete"
 	@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,9 +8,7 @@ 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` |
+| 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,11 +271,8 @@ This connector implements the following Zendesk API modules:
 
 ## Deployment
 
-This connector is deployed to:
-
-- **EC2**: `hasna-prod-connect-zendesk`
-- **Database**: `hasna-prod-connect-zendesk`
-- **S3**: `hasna-prod-connect-zendesk`
+This connector runs as a systemd service behind the deployment's own reverse proxy.
+Deployment resource names are not published with this package.
 
 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>`.

package/connectors/zendesk/SCAFFOLD.md

@@ -33,16 +33,17 @@ 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-host>/{name}` | `https://connect.example.com/notion` |
 
 ## Project Structure

package/connectors/zerosettle/package.json

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

package/connectors/zoho-bigin/CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md
 
-Zoho Bigin connector for the open-connectors monorepo.
+Zoho Bigin connector for the connectors monorepo.
 
 ## Overview
 

package/connectors/zoho-campaigns/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/zoho-sign/package.json

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

package/connectors/zoho-subscriptions/CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md
 
-Zoho Subscriptions (Billing) API connector for open-connectors.
+Zoho Subscriptions (Billing) API connector for the connectors monorepo.
 
 ## Build & Run
 

package/connectors/zohoprojects/CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md
 
-Zoho Projects connector for the open-connectors monorepo.
+Zoho Projects connector for the connectors monorepo.
 
 ## Overview
 

package/connectors/zolvo/package.json

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

package/connectors/zoom-api/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/zymbly/README.md

@@ -2,12 +2,12 @@
 
 Zymbly REST API connector for aircraft maintenance work orders, parts search, maintenance notes, and scoped raw API calls.
 
-This package was rebuilt from the public Zymbly API contract and open-connectors patterns. It is not a copy of internal platform code.
+This package was rebuilt from the public Zymbly API contract and the connectors monorepo patterns. It is not a copy of internal platform code.
 
 ## Configure
 
 ```bash
-export ZYMBLY_API_KEY=REPLACE_ME
+export ZYMBLY_API_KEY=<your-api-key>
 export ZYMBLY_BASE_URL=https://api.zymbly.com/v1
 ```
 

package/connectors/zymbly/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"
   }
 }