Yep, That’s the problem automatic deployment from Heroku doesn’t work anymore and only way to push a build from Heroku to fly is to use Turboku i.e. Manual deployment.
My wild guess is that Heroku has changed the refresh token mechanism for OAUTH2 (or) client secrets of fly since the security incident and it needs to be updated.
Meanwhile, The documentation here on fly which says that builds will be automatically deployed from Heroku should be removed and perhaps a migration document from Heroku to fly would be very helpful.
If you follow that guide: make sure to check the documentation on GitHub for the postgres-migrator part – env var names and other details have changed slightly. You might also have to adjust the actual migrate command of postgres-migrator to fit your needs.
All that’s left after that is to:
fly config save to get your fly.toml if you haven’t already
Tweak the fly.toml settings
Add either:
The [buildpacks] section to fly.toml if you used Heroku Buildpacks
A Dockerfile if you want to switch over to Docker
Optionally tweaking the ENTRYPOINT or CMD, currently through
Do nothing at all if you’ve already got a Dockerfile at the root of your project
Thanks for the write up, Actually I did try to deploy directly to fly on the first day I opened this issue but it coincided with their issue at Chicago region and the deployment failed.
Next time I will try heroku deployment once just to answer jphenow and then I will deploy directly to fly.