How honeyshah624/retail-store-opensible works
OpenSible is an infrastructure and deployment automation control plane. The documented user journey starts with defining an environment, then review/approval, provisioning, configuration and deployment, followed by monitoring and controlled updates or cleanup. Its major capabilities also include reusable playbooks/templates, secrets, cost awareness, and execution history. The graph combines documented product flows with relationships visible in the supplied source index; unsampled implementation details are not treated as inspected.
Main entry points: cloud_provisioning.py Cloud provisioning · app.py API application · execution_history.py Execution history · cicd_engine.py CI/CD engine
Components 24
Operator console
- Web console
console/src/main.tsx
API and access
- API application
server/app.py - Authentication
server/auth/middleware.py - Source routes
server/api/sources_routes.py - Playbook routes
server/api/playbooks_routes.py
Automation workflows
- Source synchronization
server/services/source_sync_service.py - Git source manager
server/services/git_source_manager.py - Playbook storage
server/storage/playbook_storage.py - Playbook parser
server/playbooks/parser.py - Playbook generator
server/playbooks/generator.py - CI/CD engine
server/services/cicd_engine.py - Playbook scheduler
server/services/playbook_scheduler.py - Reusable templates
server/templates
Infrastructure operations
- Cloud provisioning
server/services/cloud_provisioning.py - Cloud providers
server/services/cloud_providers - Worker registry
server/services/worker_registry.py - Execution worker
worker/cmd/worker/main.go - Secret management
server/services/vault_service.py
Operational state
- Pipeline state
server/storage/cicd_store.py - Execution history
server/services/execution_history.py - Execution records
server/storage/executions_store.py - Execution index
server/storage/index_db.py - Cost records
server/storage/cost_store.py
Other components
- Operator
Connections 25
- Operator → Web console: defines workflow
- Web console → API application: manages operations
- API application → Authentication: uses access control
server/app.py - API application → Source routes: registers routes
server/app.py - Source routes → Source synchronization: starts synchronization
server/api/sources_routes.py - Source synchronization → Git source manager: uses Git manager
server/services/source_sync_service.py - API application → Playbook routes: registers routes
server/app.py - Playbook routes → Playbook scheduler: uses scheduling
server/api/playbooks_routes.py - Playbook storage → Playbook parser: parses YAML
server/storage/playbook_storage.py - Playbook storage → Playbook generator: generates playbooks
server/storage/playbook_storage.py - CI/CD engine → Pipeline state: updates pipeline state
server/services/cicd_engine.py - CI/CD engine → Cloud provisioning: runs provisioning
server/services/cicd_engine.py - CI/CD engine → Execution history: tracks execution
server/services/cicd_engine.py - Cloud provisioning → Cloud providers: selects provider
server/services/cloud_provisioning.py - Cloud provisioning → Worker registry: uses worker registry
server/services/cloud_provisioning.py - Cloud provisioning → Cost records: records costs
server/services/cloud_provisioning.py - Execution history → Execution records: uses execution records
server/services/execution_history.py - Execution history → Execution index: uses execution index
server/services/execution_history.py - Authentication → Worker registry: checks worker access
server/auth/middleware.py - Operator → Cloud provisioning: requests infrastructure
- Operator → Reusable templates: reuses workflows
- Operator → Secret management: manages secrets
- Operator → Execution history: reviews runs
- Operator → Cost records: reviews costs
- Operator → Execution worker: observes execution