The DevOps Roadmap for 2022 is available for free at devopsfordevelopers.io/roadmap One of the hardest things about learning is understanding how the different components work together. Using this guide, you start with a topic that interests or relates to you. At the end of the section, other related topics are shown allowing you to pick and choose your own path to DevOps mastery. Check it out and leverage the skills you learn to advance your career as a developer, sysadmin, IT Operations, QA and more!
Now youtube is flooded with lot of basics of Devops and it's hard to find some real time scenarios with the code so this kind of advance teaching is helpful for us. Thank you so much Wilbert 😎
I seem to like both, the only thing I dislike about Terraform is that you do not have any intellisense, where with Pulumi combined with ts you wouldnt even have to check the docs if you were familiar with aws. Do you remember what theme you used in this video by any chance? :)
Agreed: intellisense help is a lifesaver! I'm pretty sure the theme is Material Theme UI: Dark Purple plugins.jetbrains.com/plugin/8006-material-theme-ui
for this case both looks sane T^T) while i read terragrunt+terraform+kubernetes provider code on current office repo looks complicated '__') i could not even write it from scratch (for now) like some knowledge gap missing on my brain but i don't know what
What I am struggling with in Pulumi is how to use multiple files and map correct dependencies between reliant infrastructure. It would be great to get a tutorial on how to use multiple directories and files for different Pulumi infrastructure...
@@DevOpsForDevelopers To expand on the above, in Terraform we've got modules but how do we correctly implement a module/separated by feature or infrastructure functionally written Pulumi code.
Thanks for the sub! Gotcha. I've been wanting to do something like this, just haven't done it yet. I think there are some pretty cool scenarios to be played with here.
The Pulumi code is not valid JavaScript. Your calls creating new Pulumi objects appear to use named parameters, which is not a thing in JS unless you use destructuring, which you did not. What you showed does not match your repo, in which normal unnamed parameters are used. Is this some feature of Webstorm that allows you to use named parameters and then transpiles them, some feature of Node, some babel thing?
Check this file in the repo, I think that's the one referenced in the video: github.com/rekibnikufesin/nextjs-demo/blob/main/infra/index.js When implementing it, we're creating a new instance of the classes exposed by Pulumi. For example, to create a new S3 bucket, we instantiate a new instance of the Bucket class as seen here: github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/s3/bucket.ts Hope that helps!
Having your Devs build infra is a bad idea. Infra is not an afterthought, it requires a lot of specialized knowledge to do right. I’ve cleaned up a lot of messy, insecure infra and hard to maintain IAC when Dev was given the keys to write their own cloud deployments. In most cases, they don’t even want that responsibility
You're right: they don't want that responsibility. And I don't want to be the bottleneck. I've had success by putting in guardrails with automation so they are only responsible for supplying some parameters unique to their application (like healthcheck endpoint, DNS name, autoscaling thresholds) and let automation handle the rest.
The DevOps Roadmap for 2022 is available for free at devopsfordevelopers.io/roadmap
One of the hardest things about learning is understanding how the different components work together. Using this guide, you start with a topic that interests or relates to you. At the end of the section, other related topics are shown allowing you to pick and choose your own path to DevOps mastery.
Check it out and leverage the skills you learn to advance your career as a developer, sysadmin, IT Operations, QA and more!
Now youtube is flooded with lot of basics of Devops and it's hard to find some real time scenarios with the code so this kind of advance teaching is helpful for us. Thank you so much Wilbert 😎
Right on, glad you found it helpful!
Thanks for the comparison.
No problem!
I seem to like both, the only thing I dislike about Terraform is that you do not have any intellisense, where with Pulumi combined with ts you wouldnt even have to check the docs if you were familiar with aws. Do you remember what theme you used in this video by any chance? :)
Agreed: intellisense help is a lifesaver!
I'm pretty sure the theme is Material Theme UI: Dark Purple plugins.jetbrains.com/plugin/8006-material-theme-ui
Which IDE is this? Looks like jetbrains but which one?
Jetbrains Webstorm
Thanks, sir. This is highly needed for me at the moment
Awesome Felix, glad it was helpful!
Why don't you create an entire DevOps course? I like your tutorials simple but powerful. That's what I need to be in DevOps
for this case both looks sane T^T)
while i read terragrunt+terraform+kubernetes provider code on current office repo looks complicated '__') i could not even write it from scratch (for now)
like some knowledge gap missing on my brain but i don't know what
Stick with it. It eventually starts to make sense, and even seems reasonable!
Great video, thank you
Glad you liked it!
love it!
Right on!
Got charged as lightening after getting the notification
⚡️⚡️⚡️⚡️
What I am struggling with in Pulumi is how to use multiple files and map correct dependencies between reliant infrastructure. It would be great to get a tutorial on how to use multiple directories and files for different Pulumi infrastructure...
Right on, that's a great idea. I'll see what I can come up with.
@@DevOpsForDevelopers Preferably in Go, otherwise typescript 😅
@@DevOpsForDevelopers Sick channel my dude, just subscribed!
@@DevOpsForDevelopers To expand on the above, in Terraform we've got modules but how do we correctly implement a module/separated by feature or infrastructure functionally written Pulumi code.
Thanks for the sub!
Gotcha. I've been wanting to do something like this, just haven't done it yet. I think there are some pretty cool scenarios to be played with here.
The Pulumi code is not valid JavaScript. Your calls creating new Pulumi objects appear to use named parameters, which is not a thing in JS unless you use destructuring, which you did not.
What you showed does not match your repo, in which normal unnamed parameters are used.
Is this some feature of Webstorm that allows you to use named parameters and then transpiles them, some feature of Node, some babel thing?
Check this file in the repo, I think that's the one referenced in the video: github.com/rekibnikufesin/nextjs-demo/blob/main/infra/index.js
When implementing it, we're creating a new instance of the classes exposed by Pulumi. For example, to create a new S3 bucket, we instantiate a new instance of the Bucket class as seen here: github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/s3/bucket.ts
Hope that helps!
Having your Devs build infra is a bad idea. Infra is not an afterthought, it requires a lot of specialized knowledge to do right. I’ve cleaned up a lot of messy, insecure infra and hard to maintain IAC when Dev was given the keys to write their own cloud deployments. In most cases, they don’t even want that responsibility
You're right: they don't want that responsibility. And I don't want to be the bottleneck. I've had success by putting in guardrails with automation so they are only responsible for supplying some parameters unique to their application (like healthcheck endpoint, DNS name, autoscaling thresholds) and let automation handle the rest.