fengling/fengling-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 13 Wiki Activity
38f71d7274
fengling-platform/.planning/STATE.md
movingsam 38f71d7274 docs(03-gateway-infrastructure-update): complete plan 03 of phase 03 
- Created SUMMARY.md with plan execution details
- Updated STATE.md with current position

Plan 03 COMPLETE - Infrastructure layer updated for GwCluster.
2026-03-03 15:48:36 +08:00

3.0 KiB
Raw Blame History

gsd_state_version milestone milestone_name status last_updated progress
1.0 v1.0 milestone in_progress 2026-03-03T12:00:00.000Z
total_phases completed_phases total_plans completed_plans
3 1 4 6

Project State

Last Updated: 2026-03-03

Status

  • Phase: 03-gateway-infrastructure-update
  • Plan: 03 ✅ Completed
  • Milestone: v1.0 - Platform Foundation
  • Position: Completed Plan 03 of Phase 03

Project Context

This is the Fengling.Platform project - a multi-tenant identity and authentication infrastructure.

Current State

  • Platform layer initialized with Tenant, User, Role aggregates
  • GatewayAggregate updated - GwTenantRoute extended, GwTenant and GwServiceInstance removed
  • NEW: GwCluster aggregate added with embedded value objects (GwDestination, GwHealthCheckConfig, GwSessionAffinityConfig)
  • NEW: IClusterStore/ClusterStore - Store pattern for GwCluster
  • Manager + Store pattern established (ITenantStore, ITenantManager, IRouteStore, IClusterStore)
  • Extensions for DI registration (AddPlatformCore, AddGatewayCore)
  • PostgreSQL database with EF Core migrations

Source for Migration

fengling-gateway project (parent directory):

  • GwTenant - 租户实体 (REMOVED - use Platform.Tenant)
  • GwTenantRoute - 路由配置实体 (EXTENDED)
  • GwServiceInstance - 服务实例实体 (REMOVED - use GwCluster embedded)
  • GwCluster - 集群聚合根 (NEW)
  • GatewayDbContext with PostgreSQL

Decisions

  • Using Manager + Store pattern from existing Tenant implementation
  • Extensions-based DI registration for quick IoC setup
  • Align with existing Platform coding conventions
  • ID Strategy: GwTenant uses long ID (Platform convention); GwTenantRoute, GwCluster use string GUID IDs (YARP-compatible)
  • Cluster Design: GwCluster uses embedded value objects (Owned Entity pattern) for Destinations, HealthCheck, SessionAffinity
  • Route Update: Extended GwTenantRoute with Methods, Hosts, Headers, LoadBalancingPolicy, AuthorizationPolicy, CorsPolicy, Transforms fields

Blockers

None.

Accumulated Context

Roadmap Evolution

  • Phase 1: Gateway routing entities ✅
  • Phase 2: Platform infrastructure ✅
  • Phase 3: Gateway cluster entities (current)
    • Plan 01: Cluster entities ✅
    • Plan 02: Route update ✅
    • Plan 03: Infrastructure cleanup ✅ (just completed)

Phase 03 Progress

  • Plan 01: Gateway Cluster Entities ✅ COMPLETED
    • Created GwCluster aggregate root
    • Created GwDestination value object
    • Created GwHealthCheckConfig value object
    • Created GwSessionAffinityConfig value object
  • Plan 02: Gateway Route Update ✅ COMPLETED
    • Extended GwTenantRoute with YARP fields
    • Removed obsolete GwTenant entity
    • Removed obsolete GwServiceInstance entity
  • Plan 03: Infrastructure Update ✅ COMPLETED
    • Updated PlatformDbContext with GwCluster DbSet
    • Created IClusterStore/ClusterStore
    • Deleted IInstanceStore/InstanceStore

Pending

  • Plan 04: Gateway DI registration (update DI registration for IClusterStore)