Volume dependency on Fly App

[fermentfan]

Why do I need to reference an existing app when creating a volume even if I just want to attach a machine to it?

edit: nvm I saw that the machine itself also references an app. So I guess an app is always grouping these entities?

[OJFord]

Also you have to create the app the first with -target - it errors when it can't find it even with the implicit dependency app = fly_app.whatever.name.

[OJFord]

edit: nvm I saw that the machine itself also references an app. So I guess an app is always grouping these entities?

It's confusing, but yes that's basically it it seem, in 'Apps v2'. Previously/v1 an 'App' was a standalone/handled-for-you thing where you wouldn't have Machines as well. But now you configure your Machines and tie them together as an App.

The readme doesn't help:

app (stable, but apps will be deprecated soon. Begin to favor machines.)

Not only is it not possible to use the provider for Apps v1 in its present state, but as above it's necessary to use the 'app' it does have in order to 'favour machines'!