All this Hashicorp licence debacle mixed with being tired (sick, really) of Terraform and it's quirks (hiting its DSL limitations mostly) have made me to think on the possibility of pushing hard on my company to adopt Pulumi as I'm in a position to do so. Conceptually I quite like it and I feel it's what IAC should have been since day 1. I've seen examples and played with it at home and just wanted to hear about your real-world experiences with it: CI/CD workflow challenges, wether you're using it through Pulumi cloud or not, problems and limitations you've encountered, teams happiness. Anything.
Worth mentioning that main concern is on the human side. Specifically the low coding skills I've seen on the DevOps field that is where I belong. It scares me a bit because after the absolute garbage I've personally seen written in Terraform and other tooling (Python, Groovy, Ansible, Bash etc) I could feel that giving users the possibility of using a touring complete language with the power and flexibility it implies for managing something as crucial as infrastructure, could end up in tragedy. (Or perhaps no and actually is what we need massively to make a mindset shift, idk)
Thank you in advance.
0 comments
—
Ask HN: Are you using Pulumi for your IAC? · HackerTrans
Worth mentioning that main concern is on the human side. Specifically the low coding skills I've seen on the DevOps field that is where I belong. It scares me a bit because after the absolute garbage I've personally seen written in Terraform and other tooling (Python, Groovy, Ansible, Bash etc) I could feel that giving users the possibility of using a touring complete language with the power and flexibility it implies for managing something as crucial as infrastructure, could end up in tragedy. (Or perhaps no and actually is what we need massively to make a mindset shift, idk)
Thank you in advance.