OpenHub Ops Gateway

One doorway for controlled IDC operations.

This root page is the human-readable entry for the OpenHub Ops control plane. Use it to understand the live access route, the AI discovery endpoints, and the recommended local database proxy workflow. The AI-readable bootstrap page stays at /ai.txt. The machine-readable discovery document stays at /.well-known/openhub-ops-agent.json.

Primary Domain ops-agent.open-hub.cn
Connect URL https://ops-agent.open-hub.cn
Address Override
API Base https://ops-agent.open-hub.cn

Human Quick Start

  • Use POST /v1/login/git with a Git username and password to obtain a short-lived session.
  • Use GET /v1/catalog/projects to discover the projects registered for that Git user.
  • Use POST /v1/tasks for controlled build, deploy, or diagnose workflows. Accepted tasks auto-create a dispatch unless defer_dispatch=true is explicitly requested.
  • Use POST /v1/db/open when a local MySQL or PostgreSQL proxy is needed. Project-bound hosts may use the minimal request body.
  • Use POST /v1/db/close with just session_id when the session should be closed explicitly.

Scope Model

The root gateway is global. After login, discover the projects registered for that Git user and then operate inside that allowed set.

AI Endpoints

  • /ai.txt returns the minimal text skill for external agents.
  • /.well-known/openhub-ops-agent.json returns the structured discovery document.
  • The root page is intentionally human-readable; external agents should prefer /ai.txt and the well-known JSON.

Local DB Proxy Helper

Third-party AI tools do not need to reimplement the local proxy lifecycle. They can invoke the built-in helper and keep it attached as a long-lived local skill process. 

OPS_GIT_PASSWORD='<git-password>' opsctl open-db-proxy --gateway-url https://ops-agent.open-hub.cn --git-username <git-username> --project-id <project-id> --database-ref <database-ref> --environment dev
  • Environment variables: OPS_GIT_PASSWORD and OPS_DB_SESSION_TOKEN
  • Operator prerequisite: Install the official opsctl helper. Public DB transport is gateway-managed over standard project HTTPS entrypoints; external agents must not prompt end users for IDC SSH or kubectl details.
  • On exit, the helper closes the db session and tears down the local transport automatically.
The control plane does not expose long-lived database credentials or internal tunnel topology in discovery. The supported local database flow is: db_open -> official local helper -> db_close -> ops-runtime-gc.