Hello everyone! A long-time automation engineer he...
# general
h
Hello everyone! A long-time automation engineer here -- started with puppet, chef, and have been a huge fan of ansible for years now. Ran across this project and it really caught my attention. Looking forward to trying it out and digging deeper. Kinda looks like maybe a big steeper of a learning curve compared to ansible (I've always been more "Ops" heavy, less "Dev" in my "DevOps" career / career in general), but looks like a really powerful tool with some impressive cloud and kubernetes integrations. I've been browsing through the docs, some youtube videos, and looking at the "examples" github repo. Beyond the official documentation, out of the content that's out there, is there a particular course / tutorial / youtube series that y'all would recommend for getting starting with Pulumi?
m
Not trying to blow my own trumpet, but I have a YouTube course design specifically for IT Pros looking to get into Pulumi (although it should work for devs to) -

https://www.youtube.com/watch?v=mVwKI9oP5Z0&list=PLeh9xH-kbPPZENHLKokNd8Wwg8bvM9nHd

h
Awesome! Sounds like exactly what someone like me is looking for! Particularly not being a developer (and in spite of spending so many years working in DevOps, I don't want to be a developer 😜... very happy as an Ops guy...). Thanks!
m
I think IT Pro people do get put off by the writing real code part of Pulumi, but it really doesn't need a lot of dev knowledge, and if you've used Python scripting then you can write Pulumi in Python, or there is even the option to use Yaml, although you loose some of the power
h
I've been working with automations platforms for so long, starting with puppet (not quite OG enough to have started with CFengine), chef, and ansible, plus working with things like terraform, AWS + CloudFormation, Kubernetes for the last few years that, and CI/CD tools, along with being an old bash and php script sys admin, that I'm fairly comfortable with those things. I just always emphasize to employers I'm an ops guy and am a pretty competent scripter but not a developer (and that I recognize the significant difference between the two). But I think that's why I like automations. There is the "developer-esque" type skills that you need to have to truly use them effectively, but you don't really need to be a developer. Scripting knowledge and very fundamental programming language understanding it plenty sufficient.
Plus now any experienced Ops/DevOps engineer can leverage ChatGPT as a junior software developer, and that is more than sufficient to bridge the gaps with these kinds of tools.