5 Commits

Author	SHA1	Message	Date
taylanbakircioglu	02b1cb2bca	feat: v1.5.0 — Site Wizard (Issue #14) + ACME Diagnostic Panel (Issue #13) ... Closes #13, Closes #14. This release squashes the v1.4.0 → v1.5.0 development line. v1.4.0 shipped the ACME stability & enterprise audit (Issues #10/#11/#12). v1.5.0 builds on that foundation with two co-equal headline features plus a 22-round audit campaign hardening the prior configuration surface. License remains MIT for v1.5.0 (relicense to AGPL-3.0 lands in v1.5.2). ------------------------------------------------------------------ HEADLINE FEATURE A — ACME Diagnostic Panel (Issue #13) ------------------------------------------------------------------ A live pre-flight + post-failure diagnostic surface for every ACME order, reachable from the ACME Automation page. The panel exists to make ACME failures legible to operators who do NOT have shell access to the API host. Endpoints (`backend/routers/acme_diagnostics.py`): POST /api/letsencrypt/orders/{order_id}/diagnostics Run the full 5-check suite (DNS / port-80 / routing / account / agents) and humanize the order's `error_detail` (>=11 RFC-8555 problem types, backwards compatible with legacy plain-string failures). POST /api/letsencrypt/orders/{order_id}/diagnostics/ {check_id}/rerun Re-run a single check in place — used by the "Re-run" button on every row of the modal's pre-flight table. GET /api/letsencrypt/orders/{order_id}/events Merged event timeline combining the typed `acme_order_events` rows with correlated `user_activity_logs` entries (resource_type = 'letsencrypt_order' AND resource_id = order_id). The diagnostic modal auto-tails this timeline every 5 seconds while open. Service-level checks (`backend/services/acme_diagnostics.py`): * DNS resolution via stdlib socket.gethostbyname_ex through run_in_executor (intentionally avoiding an aiodns runtime dep for v1.5.0). * Port-80 HEAD probe, target locked to the order's domains, success on HTTP 200 OR 404, warns on egress timeout (corp egress policies routinely blackhole outbound 80 — fail-hard would be too noisy). * SSRF guard: probe refuses non-public IPs and surfaces the skip in the diagnostic result; IPv4-mapped IPv6 normalisation closes the `::ffff:169.254.169.254` cloud-metadata vector. * HAProxy routing presence check: matches the order's cluster_ids to a port-80 HTTP frontend. * ACME account validity check against `letsencrypt_accounts`. * Agent presence check (>=1 active agent in target cluster). * Every sub-check wrapped in a wall-clock timeout to bound impact on the API event loop. RBAC: ssl.read for run, ssl.read for events. Per-user 5/min rate limit on both run and rerun, backed by the (user_id, action, created_at DESC) composite index. Frontend (`frontend/src/components/ACMEAutomation.js`): * "Diagnose" button on every order row + the existing "stuck order" warning row. * Modal with two tabs: - Pre-flight Checks (Antd Table with status pills + Re-run buttons + humanized error banner) - Event Log (Antd Timeline with auto-tail polling, scroll- to-bottom, pause-on-hover) * Correlation IDs surfaced in error banners and individual check fail details for backend-log lookup. ------------------------------------------------------------------ HEADLINE FEATURE B — Site Setup Wizard (Issue #14) ------------------------------------------------------------------ A single guided flow that creates a Backend + Servers + HTTP Frontend (and optional HTTPS Frontend) in one atomic transaction. Endpoints (`backend/routers/site_wizard.py`): POST /api/site-wizard/preview — diff-preview the changeset POST /api/site-wizard/create — atomic execute POST /api/site-wizard/reject — clean rollback (including any wizard_staged ACME orders) GET /api/site-wizard/drafts — draft persistence PUT /api/site-wizard/drafts/{id} — save/update DELETE /api/site-wizard/drafts/{id} Feature surface: * One screen captures both backend (mode + servers) AND frontend (http + optional https + SSL mode) inputs. * SSL modes: ACME (new order, HTTP-01 only for v1.5.0), Upload (existing PEM), Existing (link to a stored cert), or None. * ACME-staged path: wizard_staged_until watermark on the `letsencrypt_orders` row defers finalisation until agent confirmation; per-mode reject cleanly cancels and rolls back the staged order. * Live diff preview against the cluster's current generated config (renderer-evolution noise stripped — track-sc<N> dedup, per-server cookie strip, defaults-cookie inheritance, listen-block flattening). * Draft persistence with PEM stripped at save time (private keys never round-trip through the drafts table). * Per-cluster multi-tenancy: drafts and wizard_staged orders are isolated to the creating user's cluster scope. Frontend (`frontend/src/components/SiteWizard.js`): * 4-step Antd Steps flow: Backend → Frontend → SSL → Review. * Render the live diff preview inline before commit. * Antd Form-level validation mirrors backend Pydantic validators (numeric bounds, HAProxy reserved keywords, ALPN consistency, IPv6 scope-id, domain regex, server name dedup). ------------------------------------------------------------------ AUDIT CAMPAIGN — Rounds 1 → 22 (Bulgu #1 → #82) ------------------------------------------------------------------ v1.5.0 includes 22 adversarial review passes. Each round produced its own commit set in the corporate development line; this squash collapses those into the v1.5.0 release artefact. Highlights: Round 1-4 Site Wizard core: dry-run parity, single-line value injection guard, ACL -f pattern-file block, SSL parity, timeout regex, form-state pin. Round 5-7 defaults-cookie inheritance, server-named-cookie guard, fe/be mode mismatch, duplicate server names, health_check_uri + server_address validators. Round 8-10 cookie_name / cookie_options newline-injection guard, dry-run parity (round 9), TCP-mode HTTP-only feature blockers. Round 11 SSL name path traversal + health-check >= 1. Round 12-13 SSL & ACME deep dive (Bulgu #23-#32). Round 14 single-line value injection (Bulgu #33). Round 15-17 ACME multi-tenant UX, numeric bounds, HAProxy reserved keywords, ALPN/TLS consistency, all-backup, multi-domain & multi-user enterprise edges, drain/HSTS/post-completion (Bulgu #34-#53). Round 18-21 concurrency, agent state, TCP-mode HTTP-only, list size caps, IPv6 scope-id, preview account validation, TCP backend + balance uri reject (Bulgu #54-#61). Round 22 FE error visibility + 3x stale-data lockouts, referential integrity + cascade safety, authentication & authorization, multi-cluster isolation, apply_pending_changes concurrency, script injection + bulk import multi-tenancy, prefix-stripped signature comparison (Bulgu #62-#82). ------------------------------------------------------------------ NO CORPORATE-SPECIFIC ARTIFACTS ------------------------------------------------------------------ This squash deliberately sanitises corporate hostnames, container registry references, and TLS secret names into generic placeholders (`your-registry.example.com/your-org`, `haproxy-openmanager*.example.com`, `wildcard-tls`, `taylanbakircioglu/haproxy-openmanager-*`) so the public artefact contains no internal infrastructure detail. Pilot / development history that retained those values stays in the corporate fork and is NOT part of this commit.	2026-05-14 00:04:19 +03:00
taylanbakircioglu	c2766eadbd	feat: dark mode support, UI improvements, and version bump to v1.2.0 ... - Full dark mode support across all pages with lightbulb toggle in header - Theme preference persisted in localStorage across sessions - Ant Design 5 token-based theming (40+ components updated) - Recharts dark mode: axes, grids, tooltips adapt to theme - Login page redesigned with product-consistent blue-gray palette - Overscroll bounce background matches dark theme - All Servers search with multi-field filtering - Bulk Config Import UI streamlined with collapsible guidelines - ConfigProvider moved above AppContent for correct token resolution Made-with: Cursor	2026-04-03 01:16:05 +03:00
taylanbakircioglu	199ade8ce5	Fix: Browser cache causing phantom deleted entities across all pages ... 🐛 Critical Browser Cache Bug - System-Wide Fix: - Fixed deleted entities reappearing on normal page refresh - Hard refresh (Cmd+Shift+R) worked, normal refresh showed stale cache data - Applied cache-busting to ALL entity fetch operations across entire application 🔧 Cache-Control Headers Added to 10 Components: 1. BackendServers.js - fetchBackends(), fetchFrontends(), fetchSSLCertificates() 2. FrontendManagement.js - fetchFrontends(), fetchBackends(), fetchSSLCertificates() 3. SSLManagement.js - fetchCertificates() 4. ApplyManagement.js - fetchPendingChanges() (4 API calls: frontends, backends, WAF, SSL) 5. WAFManagement.js - fetchFrontends() 6. AgentManagement.js - fetchAgents(), fetchPools() 7. PoolManagement.js - fetchPools(), fetchPoolAgents() 8. UserManagement.js - fetchUsers() 9. Configuration.js - fetchAgents() 10. ClusterContext.js - fetchClusters() Headers Applied: 'Cache-Control': 'no-cache, no-store, must-revalidate' 'Pragma': 'no-cache' 'Expires': '0' (some components) 🎯 Impact Analysis - SAFE Changes: ✅ Only GET requests affected (POST/PUT/DELETE unchanged) ✅ Response format unchanged (only headers added to request) ✅ No breaking changes to existing functionality ✅ Performance impact minimal (entities change frequently anyway) 🛡️ Protected Against Cache: - Deleted backends/frontends won't reappear - Deleted agents won't show in lists - SSL certificates always fresh - User list always current - Cluster/Pool data always accurate 🔍 Testing Performed: - Backend API verified: Only active backends returned (is_active=TRUE) - SSL API verified: Returns 4 certificates correctly - All axios.get calls now have cache-control headers - No linter errors ✅ Root Cause Solved: Browser/Axios caching GET responses → Stale data on normal refresh Solution: Force fresh data from API on every request Impact: Phantom entities bug completely resolved across entire application	2025-11-07 11:51:14 +03:00
taylanbakircioglu	c72859d507	Fix: Add cluster_id to config requests to prevent wrong cluster selection ... - Add cluster_id column to agent_config_requests table - Update config request endpoint to accept and validate cluster_id - Frontend now sends cluster_id with config requests - Fixes issue where agents in pools with multiple clusters get wrong config requests Technical Details: - Database migration adds cluster_id as nullable foreign key for backward compatibility - Backend validates that agent belongs to requested cluster via pool_id check - Improved logging includes cluster name for better traceability - No impact on existing features (apply management, sync status, entity CRUD)	2025-10-30 12:49:30 +03:00
taylanbakircioglu	6aae0f4309	Initial commit	2025-10-27 12:14:03 +03:00