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

@@ -16,7 +16,7 @@ Enter the values under **Credentials** in KAB, for the engagement's project and
| `tenant_id` | The Entra tenant id |
| `client_id` | The app registration's id |
| `client_secret` | The client secret |
| `scope_root` | `managementGroups/<id>` or `subscriptions/<id>` |
| `scope_root` | `managementGroups/<id>`, `subscriptions/<id>`, or one resource group, `subscriptions/<id>/resourceGroups/<name>` (azure-discovery 0.1.5 or later) |
| `cloud` | Optional: `public`, `usgov` or `china` |
**For a short trial on your own estate only:** leave those three fields blank and put a token in `access_token`, from `az account get-access-token --resource https://management.azure.com --query accessToken -o tsv`. It expires within about an hour, after which calls fail until you store a new one. It carries your own permissions, not Reader, so never use this for a customer.