Making `flyctl scale` blocking?

[ignoramous]

@paws

The problem seems to be, flyctl scale works in an async manner, such that immediately subsequently calling flyctl monitor won’t work - it must be at precisely the right time. If I call flyctl monitor too soon or too late, it fails.

Sounds like you should file a GitHub issue for it: Issues · superfly/flyctl · GitHub

@paws

What might be some alternative ways to scale a Fly VM (including raw HTTP calls if needed) I should consider?

Machines (Apps v2) have leases and waits afaik, that might help you achieve this (docs).

Machines don’t yet support flyctl scale, but the equivalent is flyctl machine clone <from-this-machine> -r <region> -a app

Announcement: Fly Apps on machine prerelease