Skip to main content

Saved links, plus the one the attached environment carries.

GET 
/api/links

A link is a runtime connection, not a row — so "Dome Lite should have a SimLink" is not answered by a seed. Attaching the environment is what puts it up. Before this the pane listed sockets, and a Dome Lite exercise has none, so it sat empty through every run while three aircraft flew on an in-process link nothing named.

The assembly moved to [fleet::link_snapshots] when the integration slice started riding the picture (#300): the settings page and the picture must answer is this radio up with one number, and two assemblies would eventually disagree in front of an operator with no way to tell which was right.

Responses​

saved links plus the one the attached environment carries, with live state