Mark TASK-13 complete and document fail2ban_metadata_service

This commit is contained in:
2026-04-15 09:14:29 +02:00
parent 56c511d905
commit 6dc53a80b5
2 changed files with 6 additions and 0 deletions

View File

@@ -119,6 +119,7 @@ backend/
│ │ ├── filter_config_service.py # filter config lifecycle management
│ │ ├── action_config_service.py # action config lifecycle management
│ │ ├── log_service.py # Log preview and regex test operations
│ │ ├── fail2ban_metadata_service.py # Resolve and cache the fail2ban SQLite DB path via the fail2ban socket
│ │ ├── history_service.py # Historical ban queries, per-IP timeline
│ │ ├── blocklist_service.py # Download, validate, apply blocklists
│ │ ├── geo_service.py # IP-to-country resolution, ASN/RIR lookup
@@ -186,6 +187,7 @@ The business logic layer. Services orchestrate operations, enforce rules, and co
| `action_config_service.py` | Discovers available actions by scanning action.d/; reads, creates, updates, and deletes action definitions; assigns actions to jails |
| `config_file_service.py` | Shared utilities for configuration parsing and manipulation: parses config files, validates names/IPs, manages atomic file writes, probes fail2ban socket |
| `raw_config_io_service.py` | Low-level file I/O for raw fail2ban config files |
| `fail2ban_metadata_service.py` | Resolves the fail2ban SQLite database path by querying the fail2ban socket and caches the result for reuse across services |
| `log_service.py` | Log preview and regex test operations (extracted from config_service) |
| `history_service.py` | Queries the fail2ban database for historical ban records, builds per-IP timelines, computes ban counts and repeat-offender flags, and syncs new records into BanGUI's archive table |
| `blocklist_service.py` | Downloads blocklists via aiohttp, validates IPs/CIDRs, applies bans through fail2ban or iptables, logs import results |

View File

@@ -410,6 +410,10 @@ Duplicate imports generate linter warnings, add noise to diffs, and signal that
### TASK-13 — Document `fail2ban_metadata_service` and `history_sync` task in the architecture doc 🟡
**Status:** Completed ✅
**Summary:** Added `fail2ban_metadata_service.py` to the service documentation and confirmed `history_sync.py` is documented as delegating to `history_service.py` in `Docs/Architekture.md`.
**Where:**
`Docs/Architekture.md` — Services table (section 2.2) and Tasks table (section 2.2).