I've used Pulumi for professional projects and personal projects, and I think it's fantastic. You can write your code in pretty much any major language (professionally, i use Python, personally I use Go), and you get the same output. Running the Pulumi program itself couldn't be simpler.
My one critique is sort of weird in the sense that Pulumi supports way more than its public documentation says. I hope they up their documentation game in the future, because there are a lot of things that I had to go digging through source code to find out how to implement. But that's really a minor nitpick in the grand scheme of things. Big Pulumi fan here.
Pulumi docs engineer here. Really appreciate that feedback -- what sort of thing did you have to go digging for? We're definitely investing here so I'd love to hear more about what you were looking for and didn't find (or what you discovered along the way that we could've made clearer). Thanks!
It's been a few months, so I can't remember details, but one thing I wanted to use some features was the EventBridge Scheduler and a few other things like that, and I couldn't find anything on the website that referenced those, but I did find the relevant classes defined in the code and was able to get everything working within a few minutes. (Kudos to the comments around the code!)
I agree! Looking at the source code is invaluable. Also if you use Azure, look at the generated ARM templates, for clues on how to set things up where the docs are short on details. It is nice they don't abstract over the ARM templates too much.
Comments
I've used Pulumi for professional projects and personal projects, and I think it's fantastic. You can write your code in pretty much any major language (professionally, i use Python, personally I use Go), and you get the same output. Running the Pulumi program itself couldn't be simpler.
My one critique is sort of weird in the sense that Pulumi supports way more than its public documentation says. I hope they up their documentation game in the future, because there are a lot of things that I had to go digging through source code to find out how to implement. But that's really a minor nitpick in the grand scheme of things. Big Pulumi fan here.
Pulumi docs engineer here. Really appreciate that feedback -- what sort of thing did you have to go digging for? We're definitely investing here so I'd love to hear more about what you were looking for and didn't find (or what you discovered along the way that we could've made clearer). Thanks!
It's been a few months, so I can't remember details, but one thing I wanted to use some features was the EventBridge Scheduler and a few other things like that, and I couldn't find anything on the website that referenced those, but I did find the relevant classes defined in the code and was able to get everything working within a few minutes. (Kudos to the comments around the code!)
There are more than a few resource types lacking import examples/details in the docs.
Other than that, for most resources I use the docs are pretty good.
Yep, this, exactly.
I agree! Looking at the source code is invaluable. Also if you use Azure, look at the generated ARM templates, for clues on how to set things up where the docs are short on details. It is nice they don't abstract over the ARM templates too much.