I get CLI users, sometimes using the cli is faster and more efficient.

However I have had frequent discussions with people (all of them also avid CLI users) that set up infrastructure as code. I prefer the super understandable Gui of a tool like octopus deploy over hundreds of yaml files whose content can only be understood by doing a year long deep dive any day.

They always use the same two arguments: Infrastructure as code allows you to rebuild your entire software deployment from scratch, and the code can be versioned, thereby providing an audit trail for deployments.

In decades of software development I have exactly had to redeploy an entire network from scratch 0 times. If you're in that stage the cause is most likely hardware and re-provisioning that will probably take the bulk of your time.

About the versioning: I'm not arguing against storing deployments as yaml files, but writing them by hand is insanely inefficient. There should be a nice GUI that generates and writes these yaml files, so you don't have to know every option an value and every validation rule by heart.

Also, I am relatively certain that a tool like octopus deploy also has auditing of who deployed what software in which location.