What is the audience you're trying to target here? My project is already doing what you're attempting to demo here deploying a RKE2 cluster in AWS GovCloud and SC2S using terraform and installing applications into it using flux, all happening in Gitlab, but we are very much not doing this as a replacement for Heroku. Heroku doesn't exist and isn't even a possibility where we deploy. I don't imagine the one-man team trying to share a passion project with friends on the Internet really has the same concerns and cares about something like this.<p>For what it's worth, I kind of hate that we're using Gitlab for this, but as far as fully-integrated DevSecOps solutions that include VCS, binary artifact repositories, and pipeline orchestration all in one, there's Gitlab and there's Azure DevOps and that's it. No one else offers this, so here we are. My complain is more that, as much as I also hate Jenkins because the no database everything is configured via text files scales terrible, especially over NFS, and security is non-existent, but going from Groovy DSL to embedded bash scripts in a heredoc that is part of a yaml list object is a significant downgrade in pipeline developer experience and quality control as a vehicle for pipeline as code.<p>I really, really wish you guys hadn't gone with yaml-defined tasks as a pipeline scripting language. As bad as Jenkins is for every other reason, they really got the pipeline DSL correct.