mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
108 lines
4.6 KiB
YAML
108 lines
4.6 KiB
YAML
# MCP tool definition — tool entries are scaffolded from the OpenAPI schema.
|
|
# The tool list and operation IDs are kept in sync automatically:
|
|
# pnpm --filter=@hanzo/mcp run scaffold-yaml -- --sync-all
|
|
#
|
|
# To enable a tool, set enabled: true and add required scopes + annotations.
|
|
# All other fields (title, description, enrich_url, etc.) are yours to configure.
|
|
category: Reverse proxy
|
|
feature: reverse_proxy
|
|
url_prefix: /settings/organization-proxy
|
|
ui_apps: {}
|
|
tools:
|
|
proxy-create:
|
|
operation: proxy_records_create
|
|
enabled: true
|
|
scopes:
|
|
- organization:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: false
|
|
idempotent: false
|
|
title: Create reverse proxy
|
|
description: >
|
|
Create a new managed reverse proxy for a custom domain. Provide the domain (e.g. 'e.example.com') that will
|
|
proxy requests to Insights. The response includes the CNAME target — the user must add a CNAME DNS record
|
|
pointing their domain to this target. Once DNS propagates, the proxy is automatically verified and an SSL
|
|
certificate is issued. The proxy starts in 'waiting' status until DNS is verified.
|
|
exclude_params:
|
|
- target_cname
|
|
- status
|
|
- message
|
|
- created_at
|
|
- updated_at
|
|
- created_by
|
|
proxy-delete:
|
|
operation: proxy_records_destroy
|
|
enabled: true
|
|
scopes:
|
|
- organization:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: true
|
|
idempotent: true
|
|
title: Delete reverse proxy
|
|
description: >
|
|
Delete a managed reverse proxy. For proxies still being set up (waiting, erroring, timed_out), the record is
|
|
removed immediately. For active proxies, a cleanup workflow is started to remove the provisioned
|
|
infrastructure.
|
|
proxy-diagnose:
|
|
operation: proxy_records_diagnose_create
|
|
enabled: true
|
|
scopes:
|
|
- organization:write
|
|
annotations:
|
|
readOnly: true
|
|
destructive: false
|
|
idempotent: false
|
|
title: Diagnose reverse proxy
|
|
description: >
|
|
Run a deep diagnostic on a reverse proxy that's stuck or erroring. Inspects the customer's CNAME, the
|
|
certificate provider's hostname state, CAA records walked up the DNS tree (the most common stuck-validation
|
|
cause), HTTP-01 challenge reachability, a live event probe, and certificate expiry. Returns a structured
|
|
report with each check's status and concrete remediation steps — including the exact DNS records the
|
|
customer should add when CAA blocks issuance. Use this when proxy-get returns an erroring or timed_out
|
|
status, or whenever a user asks why their proxy isn't working.
|
|
proxy-get:
|
|
operation: proxy_records_retrieve
|
|
enabled: true
|
|
scopes:
|
|
- organization:read
|
|
annotations:
|
|
readOnly: true
|
|
destructive: false
|
|
idempotent: true
|
|
title: Get reverse proxy details
|
|
description: >
|
|
Get full details of a specific reverse proxy by ID. Returns the domain, CNAME target (the DNS record value
|
|
the user needs to configure), current provisioning status, and any error or warning messages. Use this to
|
|
debug why a proxy isn't working or to check DNS verification status.
|
|
proxy-list:
|
|
operation: proxy_records_list
|
|
enabled: true
|
|
scopes:
|
|
- organization:read
|
|
annotations:
|
|
readOnly: true
|
|
destructive: false
|
|
idempotent: true
|
|
list: true
|
|
title: List reverse proxies
|
|
description: >
|
|
List all managed reverse proxies configured for the current organization. Returns each proxy's domain, CNAME
|
|
target, provisioning status, and the maximum number of proxies allowed by the current plan. Use this to
|
|
check whether a reverse proxy is set up before recommending one.
|
|
proxy-retry:
|
|
operation: proxy_records_retry_create
|
|
enabled: true
|
|
scopes:
|
|
- organization:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: false
|
|
idempotent: false
|
|
title: Retry reverse proxy provisioning
|
|
description: >
|
|
Retry provisioning a reverse proxy that has failed. Only works for proxies in 'erroring' or 'timed_out'
|
|
status. Resets the proxy to 'waiting' and restarts the DNS verification and certificate provisioning
|
|
workflow.
|