Deploying Cloud Infrastructure using Pulumi
summary
Compares ARM and Terraform then shows Pulumi used with Azure and .NET to compile C# code into resources: creates a Resource Group, storage account, App Service and SQL Server, and provisions Cloudflare DNS to bind a custom domain; demos run with Pulumi up and show a live diff via Pulumi preview and an audit trail in the Pulumi console. Claims: general-purpose languages + SDKs simplify loops/conditionals and adoption; caveats: provider lag, state management, naming suffixes, occasional DNS propagation failures; notes Automation API and console is paid while core Pulumi is OSS.
AI-written summary · about
chapters (21)
- 0:00Start
- 0:33Introductions
- 2:15Provisioning the Resources
- 3:53Infrastructure as Code
- 4:18Cloud Providers
- 4:54Arm Template
- 5:11Creating a Parameter
- 6:17Creating the Resources
- 9:04Terraform
- 9:36Example of Creating a Storage Account Using Terraform
- 10:28State Management
- 11:36Conditional Logic
- 16:25Kubernetes Provider
- 26:40Third-Party Apis
- 29:16Import Existing Resources
- 30:23Automation Api
- 33:24Team Pricing Tier
- 34:29Challenges
- 34:58Learn the Cloud Providers Resource Apis
- 39:18Demos
- 52:02Tls Custom Certificate
related talks
53mInfrastructure as code - is it really?
53mInfrastructure as Code on Azure: Bicep vs Terraform vs Pulumi
02h 31mPulumi, or How to Manage Your Infrastructure with Your Favorite Language
01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
08mInfrastructure as code in any programming language
58mTake control of your cloud environment using IaC with Pulumi
01h 02mBeyond infrastructure as code DSLs
27mEvaluating Your Toolbox