How svuillaume/forticnapp_cloud_integrations works
This repository is a web-based Azure onboarding agent for FortiCNAPP. A user chats with the agent or uploads an Azure preflight report; the agent consults an LLM and routes tool calls to Azure and FortiCNAPP MCP services. Onboarding progresses through environment checks, integration discovery/validation, and—only after user confirmation—account creation and verification. The graph also shows the API, tool-routing, and service-client layers. The README is empty, and some implementation excerpts are partial, so uncertain connections are omitted.
Components 18
Chat and API
- Chat UI
- Web API
Agent Runtime
- Session State
- Agent Loop
- LLM Client
- Tool Router
- MCP Hub
Azure Onboarding
- Preflight Report
- Azure Preflight
- Azure MCP
FortiCNAPP Integration
- FortiCNAPP MCP
- Account Operations
- REST Client
Other components
- User
- Bifrost Gateway
- Azure CLI
- Azure Key Vault
- FortiCNAPP API
Connections 23
- User → Chat UI: uses
- Chat UI → Web API: sends requests
- Web API → Session State: gets session
- Web API → Agent Loop: runs turn
- Web API → Preflight Report: stores upload
- Web API → Tool Router: executes confirmed action
- Agent Loop → Session State: updates messages
- Agent Loop → LLM Client: requests completion
- LLM Client → Bifrost Gateway: sends model request
- Bifrost Gateway → LLM Client: returns completion
- Agent Loop → Tool Router: dispatches tool calls
- Tool Router → Preflight Report: reads uploaded report
- Tool Router → MCP Hub: calls remote tool
- MCP Hub → Azure MCP: dispatches Azure tools
- MCP Hub → FortiCNAPP MCP: dispatches account tools
- Azure MCP → Azure CLI: runs commands
- Azure MCP → Azure Preflight: runs preflight
- Azure CLI → Azure Key Vault: stores secret
- Account Operations → Azure CLI: resolves Key Vault reference
- FortiCNAPP MCP → Account Operations: calls operations
- Account Operations → REST Client: requests account data
- REST Client → FortiCNAPP API: calls REST API
- FortiCNAPP API → REST Client: returns API data