Add hyperscaler discovery MCP servers and Well-Architected guidance
Some checks failed
check agents / check (push) Failing after 12s
Some checks failed
check agents / check (push) Failing after 12s
azure-discovery, aws-discovery and gcp-discovery collect read-only metadata on servers, workloads, Kubernetes clusters, networks, data stores, policies and provider recommendations. Credentials arrive per call from the vault. Replies are paged, scrubbed of secrets and anonymised, and throttled calls back off. cloud-knowledge searches each provider's Well-Architected guidance from fixed lists only, so no customer detail can leave the platform. Adds shared skills, the render and test tooling, a public Python Dockerfile until the hardened base image is reachable, the customer access guide, the implementation plan and the Vault Service platform issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -82,3 +82,13 @@ agents:
|
||||
mcp_servers:
|
||||
alz-discovery-sample:
|
||||
port: 8110
|
||||
# Read-only customer discovery. Customer credentials reach these per call from the vault, never from here.
|
||||
azure-discovery:
|
||||
port: 8111
|
||||
aws-discovery:
|
||||
port: 8112
|
||||
gcp-discovery:
|
||||
port: 8113
|
||||
# Well-Architected guidance. Its connection is Kyndryl's, stored tenant-wide.
|
||||
cloud-knowledge:
|
||||
port: 8114
|
||||
|
||||
Reference in New Issue
Block a user