Suggestion: Machine naming convention for human operators

[ignoramous]

@containerops

The autogenerated machine names are random and lack any meaningful information.

It’d have been okay if it were random, but they aren’t. There’s information packed in those IDs. I think, for ops where flyctl / the api endpoint requires machine-ids, it could also accept machine-names, which are their human-readable counterpart.

Prior art:

@ignoramous

It’d be nice if we could use Machine names instead of IDs that increasingly have a lot of hex chars common for some reason. I always have to double check the ID before execing some of the more onerous commands (remove -f for example): [FR] flyctl m update with machine-name · Issue #1293 · superfly/flyctl · GitHub (I volunteer to impl if this is something that folks at Fly are open to merging).