Was it so bad? My experience with it was resoundingly positive, and saw lots of productivity gains with a great developer experience for teams that could build apps with strong guard rails in place.

Now everyone and the kitchen sink „needs“ their own kubernetes cluster and operations teams struggle to build complex landing zones for the underlying cloud infrastructure so teams don’t shoot their own foot off all too easily…

For context: I was at a company that was trying to roll out OpenStack internally (don't do this). Lots of stuff got thrown at the wall in an attempt to find a unified provisioner, nearly all of it terrible. Thankfully my role was that of a consumer.

My recollections were that BOSH and CF exposed a ton more complexity than I wanted, and I don't remember there being a great story for deploying Rails apps. But all of these abstraction layers are just like cross-platform GUI toolkits – you're never going to approach the native look and feel or integration. And I don't like the terminology(!) it's all relatively unintuitive to me (e.g. stem cells, deployments, releases).

For contrast the Hashicorp stack for our AWS environments (tf+packer+vault) generally felt much more pleasant to deal with, and that's where the comparison to GUI toolkits falls apart I suppose.

But… look at all the integrations and enterprisey features that CF+BOSH offer. That's way more of the sort of thing that I'd expect to fit in at Salesforce.

Agreed on the complexities of CloudFoundary, there’s a ton of work going on behind the scenes to make it work.

That said I think the Hashistack doesn’t address the PaaS component. There’s no cf push with HashiCorp tools.

It’s early days but maybe WayPoint will make that happen.