Terraform Cookbook (for True Epub) (Kerim Satirli Taylor Dolezal)（Z-Library）

【One-Line Pitch】 A recipe-driven guide to running Terraform as a real production practice—not just writing HCL, but structuring state, modules, CI, policy, and multi-platform deployments. Best for platform, DevOps, and infrastructure engineers who already know Terraform basics and want battle-tested patterns. 【Book Arc】 - **Opening (~0%–9%)**: Frames the shift from manual provisioning to codified infrastructure, and—importantly—when *not* to reach for Terraform (single servers, single-provider IaaS, PaaS). Sets up providers, backends, and version-controlled repos. - **Early (~9%–32%)**: Builds the working toolkit: variables and abstraction, built-in functions and expressions, code-quality tooling like TFLint, policy-as-code with Open Policy Agent, and the fundamentals of reusable modules. - **Middle (~32%–55%)**: Moves into real platforms—provisioning EKS and defining Kubernetes resources in HCL, deploying Helm charts, running Nomad jobs, and managing remote state through HCP Terraform with access controls. - **Late (~55% onward)**: Turns to operational concerns: cost management and Sentinel policies, secrets retrieval from Vault, and integrating Terraform into team workflows. - **Ending**: The excerpts do not cover the closing chapters, so the final recipes and any wrap-up material are not represented here. 【Key Takeaways】 - **Know when Terraform is the wrong tool** (Opening): single-server setups, single-provider IaaS, and PaaS platforms often have simpler native options. Choosing correctly up front saves real complexity. - **Providers are the integration layer** (Opening): pick from the Registry, declare and configure the provider, then consume it in resources—this is the core loop for reaching any cloud or SaaS API. - **State is the operational heart** (Opening–Middle): remote backends (S3 + DynamoDB locking, Azure Blob, GCS, HCP Terraform) enable locking, access control, and team consistency; local state invites loss and leaked secrets. - **Functions and expressions do real work** (Early): string cleaning (`trimspace`, `chomp`), case handling (`title`, `upper`, `lower`), and network math (`cidrsubnet`, `cidrhost`) let you compute values instead of hardcoding them—but nested functions hurt readability. - **Validation and policy catch mistakes early** (Early): variable `validation` blocks enforce input rules, while TFLint and OPA/Rego policies catch deprecated syntax and provider-specific violations that `terraform validate` misses. - **Modules are the unit of reuse** (Early): focused scope, flexible variables, useful outputs, a README, and versioning—plus a test directory with example configurations—turn one-off code into a shared asset. - **Terraform reaches into Kubernetes and beyond** (Middle): the Kubernetes, Helm, and Nomad providers let you manage cluster workloads and releases alongside the infrastructure that hosts them, with variables for replica counts and image versions. - **Secrets and cost deserve first-class treatment** (Late): prefer environment variables, shared credential files, or IAM roles over hardcoded keys; retrieve secrets from Vault via data sources; use cost estimation and Sentinel policies to govern spend. 【Reading Tips】 - Treat this as a reference, not a linear read: jump to the recipe matching your current problem, then read its "Discussion" for the *why*. - Deep-read the state, module, and secrets sections—these are where production incidents originate; skim the provider-specific examples you don't use. - Clone the companion recipes repository and run examples as you go; the book explicitly encourages following along. - Watch for the recurring caution that nested functions and overly clever expressions become unmaintainable—favor intermediate locals. - Note the security guidance on credentials carefully; the book flags several "better than hardcoding, but not recommended" patterns. 【Coverage Limits】 This guide is synthesized from stratified excerpts covering roughly the first half of the book; later chapters, the closing material, and any specific recipes beyond those sampled are not represented.