[gkoberger]

I think you're underestimating the complexity of our codebase. Aside from the usual blockers, we have hundreds of repos (our Staging feature for Enterprise allows customers to deploy our code on their own cadence) all tied together using pipelines.

We have our own custom release management software, which now doesn't work. Different repos have to go out at the same time so things don't break. Plus, we extensively use their review apps for code reviews, which we've lost access to.

Lastly, not everyone has access to deploy directly to Heroku, so not everyone would be able to 'git push heroku main'.

Could we fix all of this and get it working? Yeah. But we want to be focusing on building our product, which is why we pay Heroku a ton of money so we don't have to worry about this.

[raverbashing]

Sounds like you needed to start look into migrating into a hosted k8s solution (AWS or whatever), which will probably be quicker than waiting for Heroku

Edit: ah I see you're looking into moving already

[nicoburns]

We were in the same position (although luckily far fewer repos than you!). It took a bit of fiddling, but in the end I found that it was actually quite easy to fix this by tacking on a force push to the main branch of the heroku git repo at the end of our existing CI process (essentially treating heroku got as a deploy api that happens to use the git protocol)

Don’t blame you for wanting to move, but you might find that approach helpful as a quick fix.