feat: add platform terraform for GKE deployment

[vargas-jr]

Summary

Terraform configuration for deploying Vellum Assistant to GKE with assistant.vellum.ai domain.

Architecture

assistant.vellum.ai
       ↓
Cloud Load Balancer (Static IP + SSL)
       ↓
GKE Ingress
       ↓
Next.js Pods (autoscaling)

Added

/platform/terraform/

• main.tf - GCP provider, GKE cluster (optional), static IP, managed SSL cert
• k8s.tf - Kubernetes deployment, service, ingress
• variables.tf - Configurable inputs
• outputs.tf - IP address, DNS instructions
• terraform.tfvars.example - Example configuration

/web/

• Dockerfile - Standalone Next.js build
• .dockerignore
• src/app/api/health/route.ts - Health check endpoint

Features

• Flexible: Use existing GKE cluster or create new one
• Production-ready: Health checks, resource limits, autoscaling
• Secure: Managed SSL, secrets via TF vars
• Simple DNS: Just point A record to static IP output

Usage

cd platform/terraform
cp terraform.tfvars.example terraform.tfvars
# Edit terraform.tfvars
export TF_VAR_database_url="postgresql://..."
export TF_VAR_anthropic_api_key="sk-ant-..."
terraform init && terraform apply

---

[devin-ai-integration]

Devin Review found 1 potential issue.

View 5 additional findings in Devin Review.

[devin-ai-integration]

🔴 Removal of outputFileTracingIncludes breaks runtime file access in standalone build

The PR replaces the entire next.config.ts content, removing outputFileTracingIncludes which was required to include agent-templates/**/* in the Next.js output trace. With output: "standalone", Next.js uses file tracing to determine which files to bundle into the standalone output. Since agent-templates files are read dynamically at runtime via path.join(process.cwd(), "agent-templates", agentType) (web/src/lib/gcp.ts:132, web/src/lib/gcp.ts:211), the file tracer cannot detect these dependencies.

Root Cause and Impact

The original config had:

outputFileTracingIncludes: {
  "/api/agents": ["./agent-templates/**/*"],
}

This explicitly told Next.js to include the agent-templates directory in the standalone output for the /api/agents route. The new config only has output: "standalone" with no trace includes.

In web/src/lib/gcp.ts, multiple functions read from agent-templates at runtime:

• generateAgentFiles() at line 132-133: const templateDir = path.join(process.cwd(), "agent-templates", agentType); const filePaths = readDirectoryRecursive(templateDir);
• uploadAgentConfigToGCS() at line 211: const templateDir = path.join(process.cwd(), "agent-templates", agentType);

Without outputFileTracingIncludes, the standalone build will not include these template files, causing ENOENT errors at runtime when any agent creation or configuration API is called. The output: "standalone" setting should be kept (it's needed for the Docker build), but outputFileTracingIncludes should also be preserved.

Impact: All agent creation and configuration endpoints will fail with file-not-found errors in the Docker/standalone deployment.

Suggested change

	output: "standalone",
	output: "standalone",
	outputFileTracingIncludes: {
	"/api/agents": ["./agent-templates/**/*"],
	},

---

Was this helpful? React with 👍 or 👎 to provide feedback.