Platform scripts, MCP servers, deployment and docs for the KAB runs

- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with
  --input name=@file), store per-project discovery connections, bootstrap agent MCP keys,
  refresh the KAB token, publish reports and build estate snapshots.
- Hyperscaler discovery servers extended in place; cloud-knowledge folded into them.
- deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents.
- Platform issue write-ups and current-wiring notes under docs/platform-issues/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent c14a94f33b
commit f659564208
71 changed files with 2818 additions and 2821 deletions

View File

@@ -2,7 +2,7 @@
Read-only discovery of a customer's Google Cloud estate - servers, workloads, Kubernetes clusters, networks, data stores, policies and Recommender findings - through Cloud Asset Inventory.
**Version:** 0.1.1
**Version:** 0.1.4
**Server ID:** gcp-discovery
**Port:** 8113
@@ -64,6 +64,7 @@ python server.py
- **gcp_list_organization_policies**: List Organization Policy constraints set at the scope root, or VPC Service Controls perimeters.
- **gcp_list_resource_policies**: List IAM policies set on resources under the scope root. People and groups are anonymised; service accounts stay.
- **gcp_list_recommendations**: List Recommender findings for one project, each with a common Well-Architected pillar.
- **gcp_search_well_architected**: Search the Google Cloud Well-Architected Framework's guidance by pillar and topic. Both come from fixed lists, so no customer detail leaves the platform. Uses this connection's own credential.
---
@@ -104,7 +105,9 @@ This server does not hold credentials for its upstream. The MCP Gateway reads th
| Field | Required | Secret |
|---|---|---|
| `scope_root` | yes | no |
| `service_account_json` | yes | yes |
| `quota_project` | no | no |
| `service_account_json` | no | yes |
| `access_token` | no | yes |
- In your tool code, read the connection with `get_connection()`, and reuse an upstream client with `get_upstream_client("<client kind>", build)`, which keeps one per kind and distinct connection.
- `REQUIRE_VAULT_CONNECTION` (default `true`): a call that arrives without a connection is refused, instead of using this server's own environment. Set it to `false` only for local runs.