Has anyone had success proxying to Machines created via the machines API and the fly-replay header? I’m trying to do something akin to:
Application A: Receive request, create Machine in Application B
Application A: Wait for Machine to run, register its ID in shared database, forward reference R to caller
Caller: Request R from Proxy Application C
Proxy Application C: Respond with
fly-replay: app=Application B;instance=ID
But this doesn’t seem to work, and the proxy responds with
no known healthy instances found for route tcp/443. Which is weird, because the machine created in Application B registers only with an internal port of 80, and 443 is only relevant due to Proxy Application C terminating SSL.
My use case here is that Application B may have many dynamically created machines spawned within it, and Proxy Application C is responsible for service discovery from callers. This seemed like a valid use case based on how fly-replay is documented, but this doesn’t seem to be working at all. Has anyone had any luck here, or similar problems?