Apps v2 - don't let fly regions commands work on v2 apps.

[catflydotio]

We don't use the region pool in Apps v2, but I can create one for my v2 app:

$ fly regions set lhr
Region Pool: 
lhr
Backup Region: 

[catflydotio]

Update: I think @dangra is going to add some V2 functionality to fly regions commands. There may still be cleanup to do after that, though.

[gbraad]

@catflydotio: I filed an issue (superfly/fly#300) ^^^, which probably ended up in the wrong repo. The command fly regions and fly scale act in very unexpected ways.

Especially, as fly deploy always seems to deploy 2 machines in the region, after I have used fly regions (even with a single 'primary' location).

Please have a look at the issue and let me know if more information is needed.

[catflydotio]

@gbraad As it stands, the region pool is not used by Apps V2; instead the app's regions are defined by where it has Machines. Hence this issue.

There's a new doc to explain how to use fly scale with Apps V2: https://fly.io/docs/apps/scale-count/

fly deploy deploys 2 Machines for resilience purposes. If the process group has services, Fly Proxy can autostart and autostop its Machines according to the concurrency settings you choose (https://fly.io/docs/apps/autostart-stop/). If the process group has no services, a second standby Machine is created but will only start in the case of the first Machine experiencing a host failure.

[gbraad]

Thanks for the links. This explains a lot about the behaviour I see.