Solution architecture outcome pattern: agent and its MCP servers
Some checks failed
check agents / check (push) Failing after 13s
Some checks failed
check agents / check (push) Failing after 13s
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate stream from the individual and sub-agent patterns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: <placeholder_for_mcp_server_name>-config # Do not modify, this will be replaced during deployment by the CI/CD pipeline
|
||||
data:
|
||||
|
||||
# Read by the CI/CD pipeline: the server's name, and the port it listens on
|
||||
# (used for the container, the Service and the probes)
|
||||
MCP_SERVER_NAME: "solution-architecture-aws"
|
||||
SERVER_PORT: "8117"
|
||||
|
||||
# One JSON object per line; LOG_FORMAT=console prints readable lines
|
||||
LOG_LEVEL: "INFO"
|
||||
LOG_FORMAT: "json"
|
||||
|
||||
# Leave on. The Gateway authenticates to this server with a bearer token, and
|
||||
# turning this off makes every tool callable by anything that can reach the
|
||||
# pod inside the cluster.
|
||||
REQUIRE_AUTH: "true"
|
||||
|
||||
# Refuse a call that arrives without the tenant's credential from the Vault Service
|
||||
REQUIRE_VAULT_CONNECTION: "true"
|
||||
|
||||
# Add your own settings here
|
||||
# EXAMPLE_SETTING: "value"
|
||||
Reference in New Issue
Block a user