feat: add upstash-api-platform connector#132
Conversation
Implement @hasna/connect-vault for self-hosted Vault HTTP API access with token/namespace auth, KV v2, transit, sys, identity, and wrapping support.
Introduce @hasna/connect-upstash-api-platform with Basic-auth client for teams, vector indices, audit logs, CLI/profile support, and registry entry.
…tors/8105f7d9-af92-4158-a25e-d894f6eced55-984a464e feat: add HashiCorp Vault connector
|
Worker update for task dc463b0d-01ed-4fa3-b5de-7c16287d6482. Pushed
Validation:
Not merged by this worker: authenticated GitHub user is PR author |
|
Verifier update for task dc463b0d-01ed-4fa3-b5de-7c16287d6482. Validation still looks good for the Upstash connector implementation and hardening on head 2b31af6:
Still not mergeable by policy:
Follow-up todos: |
Summary
@hasna/connect-upstash-api-platformfor the real Upstash Developer API (https://api.upstash.com/v2) with HTTP Basic auth (email + management API key).upstash-api-platformin Developer Tools; scope excludes Redis/Kafka CRUD reserved for the siblingupstashslug.Test plan
cd connectors/upstash-api-platform && bun install && bun run typecheck && bun run build && bun testbun run typecheck(repo root)bun test src/lib/registry.test.tsbun test src/lib/installer.test.tsrgscan: noapi.upstashapiplatform.com,beepmedia,hasnaxyz,browser-use, or hardcoded secretsbun testsuite (186 CLI subprocess failures in this worktree env — pre-existing empty stdout from spawned CLI; unrelated to connector diff)