Files
orion/app/modules/__init__.py
Samir Boulahtit f1f91abe51 feat: add Celery task infrastructure for module system
Phase 4 of module migration plan:
- Add ScheduledTask dataclass for declaring Celery Beat tasks
- Add tasks_path and scheduled_tasks fields to ModuleDefinition
- Create ModuleTask base class with database session management
- Create task discovery utilities (discover_module_tasks, build_beat_schedule)
- Update celery_config.py to discover and register module tasks
- Maintain backward compatibility with legacy task modules

Modules can now define tasks in their tasks/ directory and scheduled
tasks in their definition. The infrastructure supports gradual migration
of existing tasks from app/tasks/ to their respective modules.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-27 22:52:01 +01:00

116 lines
3.4 KiB
Python

# app/modules/__init__.py
"""
Modular Platform Architecture.
This package provides a module system for enabling/disabling feature bundles per platform.
Three-Tier Classification:
1. CORE MODULES (4) - Always enabled, cannot be disabled
- core, tenancy, cms, customers
2. OPTIONAL MODULES (7) - Can be enabled/disabled per platform
- payments, billing, inventory, orders, marketplace, analytics, messaging
3. INTERNAL MODULES (2) - Admin-only tools, not customer-facing
- dev-tools, monitoring
Module Hierarchy:
Global (SaaS Provider)
└── Platform (Business Product - OMS, Loyalty, etc.)
└── Modules (Enabled features - Billing, Marketplace, Inventory, etc.)
├── Routes (API + Page routes)
├── Services (Business logic)
├── Tasks (Celery background jobs)
├── Menu Items (Sidebar entries)
├── Templates (UI components)
└── Migrations (Module-specific)
Modules vs Features:
- Features: Granular capabilities (e.g., analytics_dashboard, letzshop_sync)
Assigned to subscription tiers, gated at API route level.
- Modules: Cohesive feature bundles (e.g., billing, marketplace, inventory)
Enabled/disabled per platform, contains multiple features and menu items.
Usage:
from app.modules import module_service
from app.modules.base import ModuleDefinition
from app.modules.registry import MODULES, CORE_MODULES, OPTIONAL_MODULES
from app.modules.events import module_event_bus, ModuleEvent
# Check if module is enabled for platform
if module_service.is_module_enabled(platform_id, "billing"):
...
# Get menu items for enabled modules
menu_items = module_service.get_module_menu_items(platform_id, FrontendType.ADMIN)
# Get all enabled modules for platform
modules = module_service.get_platform_modules(platform_id)
# Subscribe to module events
@module_event_bus.subscribe(ModuleEvent.ENABLED)
def on_enabled(data):
print(f"Module {data.module_code} enabled")
"""
from app.modules.base import ModuleDefinition, ScheduledTask
from app.modules.task_base import ModuleTask, DatabaseTask
from app.modules.tasks import (
discover_module_tasks,
build_beat_schedule,
parse_schedule,
get_module_task_routes,
)
from app.modules.registry import (
MODULES,
CORE_MODULES,
OPTIONAL_MODULES,
INTERNAL_MODULES,
get_core_module_codes,
get_optional_module_codes,
get_internal_module_codes,
get_module_tier,
is_core_module,
is_internal_module,
)
from app.modules.service import ModuleService, module_service
from app.modules.events import (
ModuleEvent,
ModuleEventData,
ModuleEventBus,
module_event_bus,
)
__all__ = [
# Core types
"ModuleDefinition",
"ScheduledTask",
# Task support
"ModuleTask",
"DatabaseTask",
"discover_module_tasks",
"build_beat_schedule",
"parse_schedule",
"get_module_task_routes",
# Module dictionaries
"MODULES",
"CORE_MODULES",
"OPTIONAL_MODULES",
"INTERNAL_MODULES",
# Helper functions
"get_core_module_codes",
"get_optional_module_codes",
"get_internal_module_codes",
"get_module_tier",
"is_core_module",
"is_internal_module",
# Service
"ModuleService",
"module_service",
# Events
"ModuleEvent",
"ModuleEventData",
"ModuleEventBus",
"module_event_bus",
]