We are leaning into Fly.io for our support services, most importantly our bus message pipeline which will drive most of the comms between services. They provide a Wireguard network stack that fits nicely into our workflow.
We'll want to boot up external servers via iPXE that are provisioned with a Wireguard configuration similar to the one generated by their CLI, eg fly wireguard create. This provider borrows heavily from the official Fly CLI, mostly to reference graphQL structures because their API isn't public just yet (or possibly ever).
We are leaning into Fly.io for our support services, most importantly our
bus
message pipeline which will drive most of the comms between services. They provide a Wireguard network stack that fits nicely into our workflow.We'll want to boot up external servers via iPXE that are provisioned with a Wireguard configuration similar to the one generated by their CLI, eg
fly wireguard create
. This provider borrows heavily from the official Fly CLI, mostly to reference graphQL structures because their API isn't public just yet (or possibly ever).This provider should implement a Wireguard Terraform resource that mirrors the CRUD of the CLI here: https://github.com/superfly/flyctl/blob/master/api/resource_wireguard.go