Infrastructure as code - is it really?
summary
Compares provider templates, Terraform HCL and Pulumi by showing live C# Pulumi code that compiles into a resource graph, creates an Azure resource group and storage account, updates tags, enables static website hosting by calling the Azure SDK, and then destroys the stack — all successful in the demo. Notes tradeoffs: Pulumi uses real languages, fewer providers than Terraform, state files and possible mid-deploy inconsistencies, a paid Pulumi console, and the new policy as code option for governance.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:39About the speaker
- 2:26Portal provisioning
- 4:20Infrastructure as code
- 7:27Pros and cons of IaC
- 10:05Terraform overview
- 13:14Complex scenarios in IaC
- 16:26Infrastructure as software
- 19:29Getting started with Pulumi
- 22:25Deploying with Pulumi
- 24:05Updating and destroying
- 26:21Pulumi architecture
- 29:27Pulumi console demo
- 30:14Third-party APIs
- 34:31Real-world scenario
- 41:21Components and policy
- 44:33Pros and cons of Pulumi
- 47:49C# SDK vs Pulumi
- 50:15Conclusion and Q&A
related talks
08mInfrastructure as code in any programming language
58mDeploying Cloud Infrastructure using Pulumi
53mInfrastructure as Code on Azure: Bicep vs Terraform vs Pulumi
41mInfra as Code with Pulumi
20mInfrastructure as True Code with Pulumi
44mInfrastructure from Code: The Next Generation of Cloud Management
48mInfrastructure as Code with Terraform on Azure
01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi