At large, the problem with on prem in this will be that a lot of the items in any of these "infrastructure as code" tools abstract a ton of things a human will have to do. Unless you are using "on prem" to be more akin to "private overprovisioned cloud."
Adding a new machine to your setup? When is it delivered? Who is physically connecting it to power and a network rack? Adding additional storage? Same questions, basically.
All of the software that goes onto these machines can still be done this way, of course. But that is bog standard deployment scripts. Well, it was. Not sure when we changed that.
Yeah there are people who are talking about blah blah blah cloud complexity and how on-prem is some panacea. What they're really getting at is "why go through all this trouble to setup autoscaling groups and load balancers when I'm perfectly fine running things on a single Pentium II whitebox sitting in my closet?" It doesn't seem to occur to them that although that might work _for them_ the whole reason we go through this labor is we need MORE than that.
Adding a new machine to your setup? When is it delivered? Who is physically connecting it to power and a network rack? Adding additional storage? Same questions, basically.
All of the software that goes onto these machines can still be done this way, of course. But that is bog standard deployment scripts. Well, it was. Not sure when we changed that.