Connectors
A connector puts workflow forecasts into the mission control you already run, in that system's own screens and alarms, so operators never switch tools to read them.
| System | What appears there | Install | Plan |
|---|---|---|---|
| Yamcs | Events per pass, timeline bands, parameters with alarms, and a Constellation Forecast page | One jar in lib/ext and the bridge's compose file | Operator |
| Open MCT | A Constellation Forecast folder: a view per workflow, and passes as Plans for Time Strips | One script file, reading the API or Yamcs | Operator |
| OpenC3 COSMOS | A CONSTELLATION target for Limits Monitor and Grapher, and a Constellation Forecast tool | One plugin, from Admin › Plugins | Enterprise |
| Anduril Lattice | A forecast service per antenna that decides ReservePass tasks, forecast passes along their ground tracks, and rain-fade alerts | The bridge's compose file and .env | Enterprise |
| Your own system | Whatever your system holds: you write two functions, the SDK does the rest | Build a connector with the CLI, in Python, TypeScript or Go, or Receive results over plain HTTP in any language | Operator |
The plan is the one a workflow needs to deliver to that system. See Plans and limits.
How it works
Constellation Your network
────────────── ─────────────────────────────────────────
Workflow run ──► Results ◄─ pulls, outbound ──── Bridge ──► Yamcs / COSMOS / Lattice
HTTPS only │
└─► Constellation Forecast view
▲ (reads only your system)
└────── check-in and delivery reports ◄─── Bridge
(shown in the Platform)
- A workflow has a mission control output naming a connection, such as
yamcs-bridge. - When a run finishes, its results for that connection go on your account's workflow results.
- The bridge for that connection, running in your network, pulls them and writes the results into your system.
- The bridge reports what it wrote. The workflow builder shows the connection as live, and what each run wrote, without anyone opening your system.
- Pull, never push. The bridge calls Constellation outbound over HTTPS. Nothing connects into your mission control.
- Your credentials stay with you. The bridge holds your system's credentials. Constellation only sees an API key with
predictions:read. - You choose where results land. Each mission control output carries a mapping: event wording and severity, the timeline band, which parameters. The bridge applies it.
- Reruns update in place. Results are keyed by their pass, so running a workflow again updates what it wrote instead of adding a copy.
Each connection reads only the results addressed to it. Constellation keeps each run for 7 days, so a bridge that was offline longer than that resumes from the oldest run it still holds, and its log says which runs expired unread. An account takes up to 50 connections.
What a connector writes
A connector writes forecasts, labelled as forecasts, and nothing else.
- Never over your own data. Your schedule, passes, telemetry and assets stay yours. Forecasts go where your system keeps proposals, plans or forecasts, or into objects of their own: Yamcs parameters in their own
ConstellationForecastsystem, aCONSTELLATIONtarget in COSMOS, forecast services in Lattice rather than a second copy of your antennas. - Propose, never schedule. A forecast pass is never written as a scheduled contact, and a rain-fade swap is advice for an operator, never an instruction.
- Never as measured telemetry. Every name, source or tag says it is Constellation's forecast.
- What an operator took is theirs. A connector stops updating a forecast once an operator has scheduled or otherwise taken it over.
Install
Every release of the public connectors repository carries the files and images each connector needs, the CLI and the SDKs. Downloads lists each file, how to verify it, and how to mirror a release for an air-gapped site. Files are at https://github.com/constellationhq/connectors/releases/download/v<version>/<file>, and images at ghcr.io/constellationhq/<bridge>:<version>. Every release is signed; constellation verify checks it.
The output's Install fold in the workflow builder gives the same steps with your API URL and the output's connection filled in.
Releases before 1.0 are pre-releases: releases/latest and the latest image tag skip them. Use the versioned links and tags.
Each bridge image keeps its state in /var/lib/constellation, a volume the compose files name, so a recreated container resumes where the last one stopped. A first start begins at the newest run for its connection, never the history. It asks the API where that run is, so the bridges need an API serving contract 1.5.0 or later; against an older one a first start stops with an error.
Compatibility and versions
Each connector release reads one item schema, and skips (and logs) a run in any other, so an old bridge never misreads newer results.
| Connectors | Item schema (constellation.schema) | Output mapping_version |
|---|---|---|
| 0.3.x to 0.7.x | constellation.item/v2 | 2 |
0.1.x and 0.2.x read constellation.item/v1 and cannot read v2.
Versions follow semantic versioning. While 0.x, a breaking change is a new minor version: reading a new item schema or mapping_version and dropping the old one, renaming or removing a setting, packet or parameter, changing what a bridge writes so existing displays or alarms stop matching, or raising the minimum version of a supported system. New packets, parameters, optional settings or system versions are a minor release; fixes are a patch.
When the API introduces a new item schema, it keeps serving the old one for at least one connector minor release, and the changelog names the release that drops it. Upgrade your bridges before then.
Tested with Yamcs 5.14.0 and 5.13.7 (the jar in stock yamcs/example-simulation, with the Yamcs bridge writing into it) and Open MCT 4.3.1 (stock Open MCT in headless Chromium), all against a stub Constellation API. The COSMOS plugin is not tested in a COSMOS: CI builds the gem and unit tests the bridge's Python, but never installs it into COSMOS. The Lattice bridge is tested only against a stub of the Lattice routes it calls, never a real Lattice. Contract and versioning has the full table: each release against the contract, the fleet agent and the language runtimes.
The connectors are open source under the Apache License 2.0. Yamcs, OpenC3 COSMOS, Open MCT and Anduril Lattice are their owners' products, under their own licenses.
Related
- Connect Yamcs, COSMOS or Lattice to forecasts: the short version of this section
- Rain fade at ground stations: the swaps connectors deliver
- MODCOD planning for VCM and ACM: the plans connectors deliver