Lab Platform Connections: Verify Changes Before They Hit Production
A change you verified in a lab is a change you can trust in production.
The safest place to prove a change works is a lab that mirrors production. The /lab page lets you register lab platform connections, test them, and run verifications as part of a change lifecycle.
Adding a connection
- Pick a provider and enter the API endpoint.
- Reference your credentials by Vault path — secrets never live in the connection record.
- Inline validation flags a malformed endpoint or missing reference before you can save.
Test connection
Each connection has a Test button that performs a lightweight reachability check and reports status. The check routes through an SSRF guard — HTTPS only, with loopback, private, and cloud-metadata hosts blocked — so a lab URL can never be used to probe internal infrastructure.
Running a verification
With a connection active, runLabVerification launches a verification tied to a change lifecycle and records the result (and any packet-capture reference) against your workspace.
Was this helpful?
Generate scripts for the task covered in this post
Describe what you need and NAPT writes production-ready automation in Netmiko, NAPALM, or Nornir.
Open Script Generator →Related posts
Compliance Without the Spreadsheet: Continuous Posture for Network Devices
The Compliance panel runs your hardening rule packs across the fleet, scores devices, and tracks drift so audits start with evidence, not promises.
Read →Inventory & IPAM: The Source of Truth Your Scripts Actually Trust
Upload a CSV, connect to NetBox, or generate an IP range — Inventory normalises every source into the same validated row shape for the platform.
Read →Runbooks: Living Documents That Run
Runbooks combine narrative, parameters, and executable scripts so on-call engineers stop choosing between reading the doc and fixing the problem.
Read →