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:
19
mcp-servers/_common/Dockerfile.python
Normal file
19
mcp-servers/_common/Dockerfile.python
Normal file
@@ -0,0 +1,19 @@
|
||||
# Builds any server in this folder on the public python image, for when the template's base image isn't reachable:
|
||||
#
|
||||
# podman build -f mcp-servers/_common/Dockerfile.python -t <server>:<version> mcp-servers/<server>
|
||||
#
|
||||
# The rendered Dockerfile builds on the platform's hardened base, and this doesn't: it's a larger image, with pip
|
||||
# and a full Debian userland. Replace it with the rendered Dockerfile once the base image is available.
|
||||
FROM docker.io/library/python:3.13.16
|
||||
|
||||
WORKDIR /app
|
||||
COPY requirements.txt constraints.txt ./
|
||||
RUN pip install --no-cache-dir -r requirements.txt -c constraints.txt \
|
||||
&& useradd --uid 1000 --no-create-home --shell /usr/sbin/nologin mcp
|
||||
COPY server.py mcp_connection.py ./
|
||||
|
||||
ENV LOG_LEVEL=INFO
|
||||
ENV LOG_FORMAT=json
|
||||
|
||||
USER 1000
|
||||
CMD ["python", "server.py"]
|
||||
Reference in New Issue
Block a user