We've seen a handful of cases in the forum where folks have experienced issues due to the implicit backup region choice made automatically.
Latest example: https://community.fly.io/t/i-also-cannot-deploy
Like there's a prompt asking for region when deploying an app, should it also ask what one wants to do about the backup region?
That way, they know what to expect (fewer cases of 'why is my thing running there').
Similarly, if a DB is being deployed, should the workflow
look for other apps in their org, and say something if app and DB are not in the same region
ask which app this relates to
Of course, feel free to remove the 'bug' label and use whatever is appropriate.
Good idea! We'll probably be dropping backup regions shortly until we can rethink it with our new Nomad-free architecture. Then we'll revisit these topics.
We've seen a handful of cases in the forum where folks have experienced issues due to the implicit backup region choice made automatically. Latest example: https://community.fly.io/t/i-also-cannot-deploy
Like there's a prompt asking for region when deploying an app, should it also ask what one wants to do about the backup region? That way, they know what to expect (fewer cases of 'why is my thing running there').
Similarly, if a DB is being deployed, should the workflow
Of course, feel free to remove the 'bug' label and use whatever is appropriate.