Terraform Engine 🚀

A premium, lightweight, production-ready, self-hosted infrastructure orchestrator with an integrated AI Chat Interface. The engine provides administrative controls to register Terraform templates (called Tasks) and exposes a REST API along with a modern, glassmorphic dashboard and an AI-powered conversational interface to provision, update, and teardown environments (called Deployments) asynchronously.

Features

• FastAPI Core: Ultra-fast endpoints for registering tasks and managing deployments.

• Async Execution: Arq worker backing (with process-level Mock fallback if Redis is missing).

• Two-Tier Caching: Near-instantaneous terraform init runs with global provider and module caching.

• Glassmorphism UI: Beautiful, fully responsive theme-aware dashboard (Light & Dark mode).

• AI Chat Interface: Built-in conversational assistant powered by Groq, OpenAI, or custom/on-prem LLMs (Ollama, vLLM) with automatic MCP tool calling.

• FSM AI Orchestrator: Deterministic Finite-State-Machine (FSM) orchestrator with Redis session persistence, single-purpose LLM subtask nodes, and structural guardrail enforcement.

• Comprehensive API: Supports PATCH updates, clean DELETE teardowns, cross-user lookups, and dependency-safe deletion with impact analysis.

• MCP Server Support: Exposes local (STDIO) and remote/network (SSE) tools for AI agents (ChatGPT, Claude, Cursor) to manage the infrastructure.

• Dependency-Safe Deletion: Automatic dependency detection on deployment deletion — blocks destruction of parent resources (e.g., Subnets, VNets) when active child deployments depend on them (HTTP 409 Conflict with impact report).

• Zero-clutter Workspace: Standard directory package hierarchy ready for GitHub and cloud hosting.

Related MCP server: ansible-mcp-server

Directory Layout

.github/
  workflows/
    ci.yml                  # Automated GitHub Actions testing flow
  PULL_REQUEST_TEMPLATE.md  # Standard pull request format
  ISSUE_TEMPLATE/           # Structured bug and feature templates
app/                        # Main application package
  agent/                    # FSM Orchestrator, Session State, LLM Client, and Nodes
  core/                     # Configurations, Auth, Database, Queue

  models/                   # SQLAlchemy database tables
  schemas/                  # Pydantic validation schemas
  api/                      # API endpoint routers (Admin, Public, Lifecycle, Chat)
  frontend/                 # Jinja2 HTML page router
  static/                   # Static CSS assets
  templates/                # Layouts, dashboard panels, and AI chat interface
docs/                       # Detailed architectural design documents
tests/                      # Re-organized pytest test suites
pyproject.toml              # UV-based Python build description
README.md                   # Project runbook

See docs/architecture.md for a detailed deep-dive into the architecture, caching schemes, AI orchestration, guardrails, and lifecycle state workflows.

Getting Started

Prerequisites

• Python: 3.12 or higher.

• Terraform CLI: Locally installed and configured.

• Redis Server (Optional): Used by arq for background queues and real-time catalog caching. Falls back to in-process mock if absent.

• LLM API Key (Optional): A Groq, OpenAI, or custom API key for the AI Chat Interface.

Setup and Installation

This project is configured using uv for fast, reliable package management.

1. Install dependencies and create virtual environment:

   uv sync

2. Activate virtual environment:

   • On Windows:

     .venv\Scripts\activate

   • On macOS/Linux:

     source .venv/bin/activate

3. Configure environment variables (create a .env file):

   # LLM Provider (groq, openai, or custom)
   LLM_PROVIDER=groq
   LLM_MODEL=llama-3.3-70b-versatile
   GROQ_API_KEY=your-groq-api-key
   
   # Optional: OpenAI
   # OPENAI_API_KEY=your-openai-key
   
   # Optional: Custom/On-Prem (Ollama, vLLM)
   # LLM_BASE_URL=http://localhost:11434/v1
   # LLM_API_KEY=not-needed
   
   # Token Optimization (recommended for free-tier APIs)
   TOKEN_OPTIMIZATION_MODE=true
   MAX_HISTORY_TURNS=2

Running the Application

1. Run the Web Server

Launch the FastAPI development server:

uv run uvicorn app.main:app --port 8080 --reload

Access the application:

• Interactive UI Dashboard: http://127.0.0.1:8080/

• AI Chat Interface: http://127.0.0.1:8080/chat

• Swagger API Docs: http://127.0.0.1:8080/docs

2. Run the Background Worker

In a separate terminal, launch the arq worker:

uv run arq app.worker.WorkerSettings

(If Redis is not running, the web server falls back to running tasks in-process asynchronously using MockArqRedis, so you do not strictly need to start a separate worker for local testing).

AI Chat Interface

The built-in AI Chat provides a conversational interface for infrastructure management. It supports:

• Multi-Provider LLM Support: Groq (free Llama-3.3), OpenAI (GPT-4o), or any OpenAI-compatible endpoint (Ollama, vLLM, LocalAI).

• Automatic Tool Calling: The LLM autonomously calls list_tasks, get_task_schema, provision_task, get_deployment_status, list_deployments, and destroy_deployment via the MCP tool definitions.

• 11 Strict Operational Guardrails: Prevent hallucinated deployments, enforce schema validation before provisioning, resolve deployment-name-to-resource-name references, block dependent resource deletion, and more.

• Token-Optimized History: Sliding-window pruning (configurable turns) with tool-result compression for low-TPM APIs.

• Dynamic Catalog Awareness: System prompt auto-populates recognized categories and providers from Redis cache at zero latency.

Model Context Protocol (MCP) Setup

This project exposes its tasks and deployments as tools through an MCP server. This allows AI clients (like ChatGPT Desktop, Claude Desktop, or Cursor) to inspect schemas and deploy infrastructure directly.

1. Running Locally (STDIO Mode)

Configure your local AI client to launch the MCP server as a subprocess:

• Command: uv

• Arguments: run --project "/path/to/project" python "/path/to/project/app/mcp_server.py"

(Note: Ensure the FastAPI web server is also running locally so the MCP server can forward requests to the API endpoints).

2. Running over the Network (SSE Mode)

When you start the FastAPI web server, the MCP server is automatically mounted and exposed via Server-Sent Events (SSE) at:

http://<YOUR_IP_ADDRESS>:8001/mcp/sse

Other devices on the same network can connect to this endpoint directly without needing to launch a local Python command.

Running Tests

To run the automated pytest suite (which covers task creation, validation, provisioning, update patches, teardown lifecycles, and dependency blocking):

uv run pytest

All tests execute against an isolated test database test_tasks.db and clean up dynamic execution files automatically.