mirror of
https://github.com/dredx/prole.git
synced 2026-09-24 19:44:33 +00:00
63185d8104
Port-forward setup was failing the installation because:
1. argocd and dashboard entries were always added to port-mapping even when
those services haven't been selected or installed yet
2. Grafana/Prometheus service names were hardcoded as kps-* but monitoring
deploys with release name "prometheus" → services are prometheus-grafana etc.
3. The grafana status poll after init_port_forwards.sh start would mark the
entire installation failed if grafana wasn't reachable
Changes:
- _build_required_port_forwards (env.py): add argocd_enabled, dashboard_enabled,
monitoring_release params; argocd/dashboard only included when enabled; grafana
and prometheus targets use f"svc/{monitoring_release}-grafana" etc.
- _sync_port_forward_mappings (actions.py): read argocd_enabled from installer
config; read MONITORING_RELEASE from Monitoring section; clean up argocd and
dashboard entries from [Port Forwards] when disabled
- run_init_scripts (services.py): port-forward step is non-fatal — failure logs
a warning and continues; blocking grafana poll removed
- 2 new regression tests (7e) covering the above invariants
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| __main__.py | ||
| argocd.py | ||
| base.py | ||
| build.py | ||
| cfg.py | ||
| cluster_nodes.py | ||
| cluster.py | ||
| database_options.py | ||
| database.py | ||
| dependencies.py | ||
| deploy.py | ||
| docker.py | ||
| environment.py | ||
| gitops.py | ||
| knoe_users.py | ||
| navigation.py | ||
| network.py | ||
| ollama.py | ||
| packaging.py | ||
| security.py | ||
| services.py | ||
| supabase.py | ||
| validate.py | ||
| welcome.py | ||