Struct MaintenanceModule 

pub struct MaintenanceModule { /* private fields */ }

Maintenance module configuration

Use the builder pattern to configure and register this module:

let maintenance = MaintenanceModule::builder()
    .with_database(pool.clone())
    .build()?;

// Unguarded full CRUD (trusted/admin); compose a guarded router for production.
let router = maintenance.all_crud_routes();

Implementations

impl MaintenanceModule

pub fn read_only_routes(&self) -> Router

The safe default route surface: full CRUD on the two benign masters (MaintenanceSchedule, MaintenanceStage), and read-only on the engine-owned tables (MaintenanceVisit, MaintenanceVisitPart, MaintenanceRequest) whose state must only change through crate::MaintenanceWriteService / crate::MaintenanceRequestWriteService.

Stage CRUD is mounted in full because stages are company-agnostic master data (shared across the fence): creating/reordering them is an administrative act with no engine invariants, and referential safety is enforced in the DB (RESTRICT on the request FK, plus the soft-delete guard raising maintenance_stage_in_use while any live request still sits on the stage).

Use this in place of the generated crate::MaintenanceModule::all_crud_routes, which mounts unguarded writes on the visit/part/request tables. Direct mirror of backbone-asset::AssetsModule::read_only_routes (CRUD on the benign master, read-only on the engine-owned financial tables).

pub fn query_service(&self) -> Arc<dyn MaintenanceQueryService>

The published read contract for sibling modules — the now-implemented crate::exports::MaintenanceQueryService over the module’s DTOs. Mirror of backbone-asset::AssetsModule::query_service.

pub fn lifecycle_routes(&self) -> Router

The validated, GL/inventory-backed visit write surface — plan/start/add-part/complete/cancel. These are the only verbs that may change a visit’s state; compose the production surface as module.read_only_routes().merge(module.lifecycle_routes()) (reads + validated writes). Do NOT merge with crate::MaintenanceModule::all_crud_routes — both mount POST /maintenance_visits.

Requires a GlPostSink and an InventoryPort supplied via the builder (crate::MaintenanceModuleBuilder::with_gl_sink / with_inventory_port); missing either is a wiring error and panics at startup. The event sink defaults to LoggingSink.

impl MaintenanceModule

pub fn builder() -> MaintenanceModuleBuilder

Create a new module builder

pub fn all_crud_routes(&self) -> Router

Mount ALL generated CRUD endpoints (12 per entity) with NO domain validation — the fully unguarded surface. A well-formed request can create invalid rows or soft-delete a referenced master out from under its dependents. Prefer a guarded composition (read + validated writes) for any real deployment; use this only in trusted/admin/seeding contexts.

pub fn routes(&self) -> Router

👎Deprecated:

mounts unvalidated generic CRUD; prefer readonly_routes() + validated writes, or all_crud_routes() for the full/unguarded surface

Deprecated alias for Self::all_crud_routes. routes() reads like “the routes” but mounts UNVALIDATED generic CRUD on every entity — a naive mount exposes unguarded writes. Compose a guarded router (read + validated writes) for production, or call all_crud_routes() to opt into the full unguarded surface explicitly.

pub fn readonly_routes(&self) -> Router

Read-only routes for every entity (GET endpoints only) — the safe base.

Generic mutation can’t reach here, so this surface cannot bypass a validated write service’s invariants. Use this as the production base and merge validated write routes (or a write service’s HTTP layer) onto it.