Turning infrastructure relationships into a setup flow
A network contains peers, peers run on hosts, and access to a host depends on its SSH key. The interface had to keep those relationships intact while letting an operator configure each part. Adding a host therefore also meant choosing how the infrastructure service would access it.
In the host setup flow I implemented, an operator could select a saved SSH key or supply a new one. For a new key, the application first created the key record and then passed its identifier into the request to add the host. Selecting an existing key reused its identifier. The form guided those choices while preserving the separate records expected by the backend.
Network setup followed the same infrastructure model: choose the hosts, distribute peers, and provide the network configuration. The screens connected those decisions to the services that performed the infrastructure operations.


