f78ada7732
Bug: Wenn der Operator eine NTP/DNS/Squid/WG-Mutation gemacht hat, wurde nur der Service neu konfiguriert + reloadet — die Auto-FW- Rules (udp/123, udp/tcp 53, tcp 3128, udp/<wg-port>) blieben aber auf dem Stand des letzten firewall-renders. Operator musste manuell 'edgeguard-ctl render-config --only=nftables' fahren. Fix: withFW-Wrapper in main.go der nach jedem Service-Reloader auch den firewall-Renderer aufruft. Service-Reload-Errors propagieren weiterhin (Aktion gilt als gescheitert), FW-Render-Errors werden nur geloggt (DB-Row ist commited, FW kann nachgezogen werden). Wirkt für: WG, Squid, DNS, NTP. (HAProxy nicht — Domains/Backends generieren keine Auto-FW-Rules.) Version 1.0.41. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
40 lines
1016 B
JSON
40 lines
1016 B
JSON
{
|
|
"name": "edgeguard-management-ui",
|
|
"private": true,
|
|
"version": "1.0.41",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "tsc -b && vite build",
|
|
"lint": "eslint .",
|
|
"preview": "vite preview"
|
|
},
|
|
"dependencies": {
|
|
"@ant-design/icons": "^6.1.0",
|
|
"@tanstack/react-query": "^5.95.2",
|
|
"antd": "^6.3.4",
|
|
"axios": "^1.13.6",
|
|
"i18next": "^25.10.9",
|
|
"i18next-browser-languagedetector": "^8.2.1",
|
|
"react": "^19.2.4",
|
|
"react-dom": "^19.2.4",
|
|
"react-i18next": "^16.6.6",
|
|
"react-router-dom": "^7.13.2",
|
|
"zustand": "^5.0.12"
|
|
},
|
|
"devDependencies": {
|
|
"@eslint/js": "^9.39.4",
|
|
"@types/node": "^24.12.2",
|
|
"@types/react": "^19.2.14",
|
|
"@types/react-dom": "^19.2.3",
|
|
"@vitejs/plugin-react": "^6.0.1",
|
|
"eslint": "^9.39.4",
|
|
"eslint-plugin-react-hooks": "^7.0.1",
|
|
"eslint-plugin-react-refresh": "^0.5.2",
|
|
"globals": "^17.4.0",
|
|
"typescript": "~5.9.3",
|
|
"typescript-eslint": "^8.57.0",
|
|
"vite": "^8.0.1"
|
|
}
|
|
}
|