motia-iii

bsiggel/motia-iii

Fork 0

Commit Graph

Author	SHA1	Message	Date
bsiggel	6c3cf3ca91	refactor(logging): remove unused logger instances and enhance error logging in webhook steps	2026-03-08 22:21:08 +00:00
bsiggel	69a48f5f9a	Implement central configuration, custom exceptions, logging utilities, Pydantic models, and Redis client for BitByLaw integration - Added `config.py` for centralized configuration management including Sync, API, Advoware, EspoCRM, Redis, Logging, Calendar Sync, and Feature Flags. - Created `exceptions.py` with a hierarchy of custom exceptions for integration errors, API errors, sync errors, and Redis errors. - Developed `logging_utils.py` for a unified logging wrapper supporting structured logging and performance tracking. - Defined Pydantic models in `models.py` for data validation of Advoware and EspoCRM entities, including sync operation models. - Introduced `redis_client.py` for a centralized Redis client factory with connection pooling, automatic reconnection, and health checks.	2026-03-03 17:18:49 +00:00
bsiggel	014947e9e0	Migrate VMH Integration - Phase 3: Core sync handlers & utilities - Added 5 core service modules: * services/notification_utils.py: NotificationManager for manual actions (412 lines) * services/advoware_service.py: Extended Advoware operations wrapper * services/espocrm_mapper.py: BeteiligteMapper for data transformation (198 lines) * services/bankverbindungen_mapper.py: BankverbindungenMapper (174 lines) * services/beteiligte_sync_utils.py: BeteiligteSync with complex logic (663 lines) - Distributed locking via Redis + syncStatus - rowId-based change detection (primary) + timestamp fallback - Retry with exponential backoff (1min, 5min, 15min, 1h, 4h) - Conflict resolution (EspoCRM wins) - Soft-delete handling & round-trip validation - Added 2 event handler steps: * steps/vmh/beteiligte_sync_event_step.py: Handles vmh.beteiligte.* queue events - CREATE: New Beteiligte → POST to Advoware - UPDATE: Bi-directional sync with conflict resolution - DELETE: Not yet implemented - SYNC_CHECK: Periodic sync check via cron * steps/vmh/bankverbindungen_sync_event_step.py: Handles vmh.bankverbindungen.* events - CREATE: New Bankverbindung → POST to Advoware - UPDATE/DELETE: Send notification (API limitation - no PUT/DELETE support) - Added pytz dependency to pyproject.toml (required for timezone handling) System Status: - 27 steps registered (14 VMH-specific) - 8 queue subscriptions active (4 Beteiligte + 4 Bankverbindungen) - All webhook endpoints operational and emitting queue events - Sync handlers ready for processing Note: Kommunikation sync (kommunikation_sync_utils.py) not yet migrated. Complex bi-directional sync for Telefon/Email/Fax will be added in Phase 4. Updated MIGRATION_STATUS.md	2026-03-01 22:19:36 +00:00

Author

SHA1

Message

Date

bsiggel

6c3cf3ca91

refactor(logging): remove unused logger instances and enhance error logging in webhook steps

2026-03-08 22:21:08 +00:00

bsiggel

69a48f5f9a

Implement central configuration, custom exceptions, logging utilities, Pydantic models, and Redis client for BitByLaw integration

- Added `config.py` for centralized configuration management including Sync, API, Advoware, EspoCRM, Redis, Logging, Calendar Sync, and Feature Flags.
- Created `exceptions.py` with a hierarchy of custom exceptions for integration errors, API errors, sync errors, and Redis errors.
- Developed `logging_utils.py` for a unified logging wrapper supporting structured logging and performance tracking.
- Defined Pydantic models in `models.py` for data validation of Advoware and EspoCRM entities, including sync operation models.
- Introduced `redis_client.py` for a centralized Redis client factory with connection pooling, automatic reconnection, and health checks.

2026-03-03 17:18:49 +00:00

bsiggel

014947e9e0

Migrate VMH Integration - Phase 3: Core sync handlers & utilities

- Added 5 core service modules:
  * services/notification_utils.py: NotificationManager for manual actions (412 lines)
  * services/advoware_service.py: Extended Advoware operations wrapper
  * services/espocrm_mapper.py: BeteiligteMapper for data transformation (198 lines)
  * services/bankverbindungen_mapper.py: BankverbindungenMapper (174 lines)
  * services/beteiligte_sync_utils.py: BeteiligteSync with complex logic (663 lines)
    - Distributed locking via Redis + syncStatus
    - rowId-based change detection (primary) + timestamp fallback
    - Retry with exponential backoff (1min, 5min, 15min, 1h, 4h)
    - Conflict resolution (EspoCRM wins)
    - Soft-delete handling & round-trip validation

- Added 2 event handler steps:
  * steps/vmh/beteiligte_sync_event_step.py: Handles vmh.beteiligte.* queue events
    - CREATE: New Beteiligte → POST to Advoware
    - UPDATE: Bi-directional sync with conflict resolution
    - DELETE: Not yet implemented
    - SYNC_CHECK: Periodic sync check via cron
  * steps/vmh/bankverbindungen_sync_event_step.py: Handles vmh.bankverbindungen.* events
    - CREATE: New Bankverbindung → POST to Advoware
    - UPDATE/DELETE: Send notification (API limitation - no PUT/DELETE support)

- Added pytz dependency to pyproject.toml (required for timezone handling)

System Status:
- 27 steps registered (14 VMH-specific)
- 8 queue subscriptions active (4 Beteiligte + 4 Bankverbindungen)
- All webhook endpoints operational and emitting queue events
- Sync handlers ready for processing

Note: Kommunikation sync (kommunikation_sync_utils.py) not yet migrated.
Complex bi-directional sync for Telefon/Email/Fax will be added in Phase 4.

Updated MIGRATION_STATUS.md

2026-03-01 22:19:36 +00:00

3 Commits