Building applications with infrastructure as code
summary
Claims that Infrastructure as Code guarantees repeatable, versioned provisioning and reduces risk by keeping configuration in a repo; demonstrates Terraform with the lenode provider, shows generating SSH keys and a lenode API token, and runs terraform init, terraform plan, terraform apply and terraform destroy. Shows importing existing resources into Terraform state, using modules and registries, and creating a Linode instance in the demo successfully, and emphasizes multi‑cloud capability and HCL/JSON/YAML choice.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:06What is infrastructure as code?
- 4:32Benefits of infrastructure as code
- 15:44Advantages to this workflow
- 19:53Terraform Registry
- 21:25Importing infrastructure into your configuration files
- 22:17Multi-cloud deployment
- 29:00Prerequisites
- 29:29Create a Linode API Token
- 30:49Initialize Terraform
related talks
36mInfrastructure as Code with Terraform
52mInfrastructure as Code with Terraform
48mInfrastructure as Code with Terraform on Azure
01h 01mTaming Infrastructure Workflow at Scale
10mInfrastructure as a Code Best Practices with Terraform
22mProvisioning an Application Using Terraform
42mHands-on with the Terraform Module for AWS Landing Zone
32mCloud Computing 101