A list of names of other formations this formation has an affinity for. This is a hint to the scheduler to place the containers running in each of these formations "close" to each other ("close" being defined in part by latency)

A list of names of other formations this formation is connected to. Two formations can communicate over their formation endpoints (the endpoints configured in the formation_endpoints section) if and only if both formations opt in to that connection by listing each other in their respective connections map)

The individual flights that make up the formation

The keys of this map are the publicly exposed endpoints of this formation and take the form http:{endpoint}. The values of this map take the form {flight_name}:{port} and describe where the traffic that hits this endpoint should be routed. For example, "http:/foo/bar": "baz:1234" means "Route all traffic from the public internet hitting the path /foo/bar on this formation's domain to the flight named 'baz' on port 1234"

The keys of this map are the privately exposed endpoints of this formation (that is, the endpoints that this formation exposes to other formations that are connected to it) and take the form http:{endpoint} or tcp:{port} or udp:{port}. The values of this map take the form {flight_name}:{port} and describe where the traffic that hits this endpoint should be routed. For example, "tcp:1234": "foo:4321" means "Route all internal tcp traffic hitting this formation on port 1234 to this formation's foo flight on port 4321". If this conflicts with flight_endpoints the configuration will be rejected

The keys of this map are the endpoints of this formation that containers within the formation can hit to communicate with one another. Containers within a formation can always communicate directly but these endpoints are load-balanced and allow for much simpler usage in many cases. The keys take the form http:{endpoint} or tcp:{port} or udp:{port}. The values of this map take the form {flight_name}:{port} and describe where traffic on that endpoint will be routed. For example, "udp:1234": "foo:4321" would mean "Route all internal udp traffic hitting this formation on port 1234 to the formation's foo flight on port 4321". If this conflicts with formation_endpoints the configuration will be rejected

A list of allowed providers. Including this argument will disallow all other providers. If not included the scheduler will use any provider it pleases to schedule this formation

A list of denied providers, providers the scheduler will never use for this formation. If this conflicts with providers_allowed (e.g. gcp is both allowed and denied) the configuration is invalid and will be rejected

A list of allowed regions. Including this argument will disallow all other regions. If not included the scheduler will use any provider it pleases to schedule this formation