mockforge-registry-server 0.3.121

Plugin registry server for MockForge
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71

// Some models and internal modules are not yet wired into routes.
// Suppress dead_code for the library crate during development.
#![allow(dead_code)]

//! Pillars: [Cloud]
//!
//! MockForge Plugin Registry Server — library crate.
//!
//! This crate is being extracted into a reusable library so that both the
//! multi-tenant SaaS binary (`mockforge-registry-server`) and the single-tenant
//! OSS admin server (`mockforge-ui`) can share the same domain models,
//! storage layer, handlers, and authentication middleware.
//!
//! Phase 0 of the extraction: expose the existing modules via `lib.rs`
//! without behavior changes. Later phases will introduce a `RegistryStore`
//! trait, a SQLite backend, and feature gates for SaaS-only integrations.

/// JWT/password auth helpers moved to `mockforge-registry-core`.
pub use mockforge_registry_core::auth;
pub mod cache;
pub mod circuit_breaker;
pub mod config;
pub mod database;
pub mod deployment;
pub mod email;
pub mod error;
pub mod fly_logs;
pub mod fly_metrics;
pub mod handlers;
pub mod metrics;
pub mod middleware;
/// Domain models now live in `mockforge-registry-core`. Re-exported here
/// so existing `crate::models::X` paths continue to resolve during the
/// cloud-core extraction.
pub use mockforge_registry_core::models;
pub mod pillar_tracking_init;
pub mod redis;
pub mod routes;
pub mod storage;
/// Storage trait + backends now live in `mockforge-registry-core`.
/// Re-exported so existing `crate::store::*` paths keep working.
pub use mockforge_registry_core::store;
/// TOTP/2FA helpers moved to `mockforge-registry-core`.
pub use mockforge_registry_core::two_factor;
/// Validation helpers moved to `mockforge-registry-core`.
pub use mockforge_registry_core::validation;
pub mod workers;

use std::sync::Arc;

use crate::circuit_breaker::CircuitBreakerRegistry;
use crate::config::Config;
use crate::database::Database;
use crate::redis::RedisPool;
use crate::storage::PluginStorage;
use crate::store::RegistryStore;

#[derive(Clone)]
pub struct AppState {
    pub db: Database,
    pub storage: PluginStorage,
    pub config: Config,
    pub metrics: Arc<mockforge_observability::prometheus::MetricsRegistry>,
    pub analytics_db: Option<mockforge_analytics::AnalyticsDatabase>,
    pub redis: Option<RedisPool>,
    pub circuit_breakers: CircuitBreakerRegistry,
    /// Backend-agnostic domain store. Handlers should migrate to this over
    /// time, in parallel with `db`, so that both Postgres (SaaS) and SQLite
    /// (OSS admin) backends can satisfy the same handler code.
    pub store: Arc<dyn RegistryStore>,
}