Demo Cnpg Local Web Ng
Testing & Qualitydemo-cnpg-local-web-ngDemo Cnpg Local Web Ng is an Agent Skill for testing & quality published in the carverauto/serviceradar repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Run ServiceRadar web-ng locally against the live Kubernetes `demo` CNPG database for dashboard, SRQL, services, and UI testing. Use when a task asks to test with live demo data, run local Phoenix against demo CNPG, validate dashboard authoring with Playwright, or avoid fragile kubectl port-forward database access.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/carverauto/serviceradar/blob/HEAD/.agents/skills/demo-cnpg-local-web-ng/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/demo-cnpg-local-web-ng, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Demo CNPG Local Web-NG
Use this skill when local elixir/web-ng must run against the live demo
namespace CNPG database instead of Docker Compose or srql-fixtures.
Quick Start
From the ServiceRadar repo root:
.agents/skills/demo-cnpg-local-web-ng/scripts/start-local-web-ng.sh
The script:
- reads current
demo/serviceradar-db-credentialswithout printing the password; - tries the GitOps-managed internal LoadBalancer VIP
192.168.6.82:5432; - falls back to the current CNPG primary node's NodePort paths, including
cnpg-rw-internal-lbandcnpg-local-dev; - validates TCP reachability before starting Phoenix;
- starts
mix phx.serverinelixir/web-ngwith small DB pools and long queue windows for WAN/LAN testing.
To only verify the live DB route without starting Phoenix:
.agents/skills/demo-cnpg-local-web-ng/scripts/start-local-web-ng.sh --check
Then use $playwright-cli against http://localhost:4000.
Known Access Paths
Permanent GitOps-managed objects:
- Service:
demo/cnpg-rw-internal-lb - Intended VIP:
192.168.6.82:5432 - NetworkPolicy:
demo/cnpg-allow-oracle-test-postgres
Current known-good fallback from 192.168.2.134:
10.0.2.11:32040viademo/cnpg-rw-internal-lb10.0.2.11:30455viademo/cnpg-local-dev
If 192.168.6.82:5432 fails but the NodePort path works, treat it as a
routing/L2 issue, not a web-ng or CNPG issue.
Browser Validation
Use the playwright-cli skill for screenshots and smoke tests:
playwright-cli open http://localhost:4000/dashboards
playwright-cli screenshot --filename=tmp/demo-cnpg-dashboard-library.png
For dashboard authoring matrix checks:
playwright-cli run-code --filename elixir/web-ng/test/playwright/dashboard_authoring_matrix.playwright.js
Keep screenshots under tmp/ or .playwright-cli/; do not commit them.
Notes
- Prefer this skill over
kubectl port-forwardfor web-ng testing againstdemo; port-forward is fragile under Phoenix startup connection churn. - Re-read Kubernetes secrets each run. Demo credentials can rotate during releases.
- Use
CNPG_HOST_OVERRIDEandCNPG_PORT_OVERRIDEonly when explicitly testing a specific route. - Stop stale local Phoenix servers before starting a new one if port
4000is already occupied.