[{"data":1,"prerenderedAt":690},["ShallowReactive",2],{"authors":3,"\u002Fblog\u002Fstandardised-terraform-practices":26,"\u002Fblog\u002Fstandardised-terraform-practices-surround":659,"\u002Fblog\u002Fstandardised-terraform-practices-related":670},[4,16],{"id":5,"avatar":6,"bio":7,"extension":8,"github":9,"meta":10,"name":11,"role":12,"stem":13,"website":14,"__hash__":15},"authors\u002Fauthors\u002Fsagar-kapoor.yml","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69609200?v=4",null,"yml","sagar-kap",{},"Sagar Kapoor","Chief Executive Officer (CEO)","authors\u002Fsagar-kapoor","https:\u002F\u002Fsagarkapoor.eu","NsLNClfs_S-SNHFEnyR6Vq_7zEc1Xxl7QLoKrk_DB6s",{"id":17,"avatar":18,"bio":7,"extension":8,"github":19,"meta":20,"name":21,"role":22,"stem":23,"website":24,"__hash__":25},"authors\u002Fauthors\u002Fsomraj-saha.yml","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31373860?v=4","jarmos-san",{},"Somraj Saha","Chief Technology Officer (CTO)","authors\u002Fsomraj-saha","https:\u002F\u002Fjarmos.dev","mDAq8GgPZv9H8en0XHAraq3aYi_v8t2ULWGqp4cp3zY",{"id":27,"title":28,"author":29,"body":30,"category":649,"cover":650,"date":651,"description":652,"extension":653,"meta":654,"navigation":189,"path":655,"seo":656,"stem":657,"__hash__":658},"blog\u002Fblog\u002Fstandardised-terraform-practices.md","How We Standardized on Terraform for Cloud Infrastructure","somraj-saha",{"type":31,"value":32,"toc":643},"minimark",[33,54,63,68,71,79,82,85,88,91,95,98,114,139,142,145,148,429,444,452,461,468,471,474,585,588,592,595,598,610,614,617,639],[34,35,36,37,47,48,53],"p",{},"In our initial days at ",[38,39,40],"strong",{},[41,42,46],"a",{"href":43,"rel":44},"https:\u002F\u002Fweburz.com",[45],"nofollow","Weburz",", manual intervention to\nprovision cloud resources on ",[41,49,52],{"href":50,"rel":51},"https:\u002F\u002Fmicrosoft.azure.com",[45],"Microsoft Azure"," was\nslowing us down. It created bottlenecks and friction across our engineering\nworkflows. Relying on manual steps simply couldn't keep pace with our rapid\ndeployment needs as we design and implemented our infrastructure requirements.",[34,55,56,57,62],{},"To eliminate configuration drift and speed up our delivery cycles, we turned to\nInfrastructure as Code principles using ",[41,58,61],{"href":59,"rel":60},"https:\u002F\u002Fterraform.io",[45],"Terraform"," to\nautomate our pipelines. In this post, we dive into practical patterns for\nwriting clean HCL configurations, managing state efficiently, and provisioning\ncloud architectures with absolute confidence as we share our experience and\nlearnings in this blog post.",[64,65,67],"h2",{"id":66},"the-before-state-the-pain-points-of-not-having-terraform","The \"Before\" State: The Pain Points of Not Having Terraform",[34,69,70],{},"Before adopting Infrastructure as Code (IaC) at Weburz, managing our cloud\ninfrastructure relied heavily on manual processes and web console adjustments.\nWhile this hands-on approach worked during our earliest phases, scaling our\narchitecture quickly exposed significant vulnerabilities in our operational\nworkflow.",[34,72,73,74,78],{},"Perhaps the biggest issue we faced with manual intervention to manage our\ninfrastructure was ",[41,75,77],{"href":76},"\u002Fblog\u002Fmanaging-infrastructure-drift","\"configuration drift\"",".",[34,80,81],{},"Without a single source of truth, manual tweaks in the cloud console; whether\nquickly adjusting a security group rule or resizing a virtual machine, created\ninvisible divergence across our environments. Over time, actual cloud\ninfrastructure drifted far from our documented configurations resulting in\ntroubleshooting issues becoming an exercise in guesswork.",[34,83,84],{},"We jokingly addressed these manual operations as \"ClickOps\" and almost always\nheld our breadth when upgrading or auditing our infrastructure. Our reliance on\nnavigating through UI menus to manually configure services introduced an\nunnecessary risk of human error. We often overlooked crucial settings stating\n\"temporary workarounds\" but making deployments non-repeatable, difficult to\naudit, and highly susceptible to mistakes that could disrupt production\nservices.",[34,86,87],{},"Over time we also realised how critical infrastructure details were stored\nprimarily in the heads of a few specific team members rather than being\ndocumented systematically. This created single points of failure; if the person\n(who set up a particular database cluster or network route) was unavailable, the\nteam faced unnecessary hurdles in modifying or scaling those resources.",[34,89,90],{},"The third issue we identified was spinning up identical deployment environments.\nSetting up staging, QA, and production environments was nearly impossible using\nour archaic manual provisioning. Small discrepancies between environments\nfrequently led to the cloud infrastructure equivalent of the classic \"it works\non my machine\" problem. Our application builds sometimes passed smoothly in the\ndeveloper's local testing environment, only to fail upon hitting production due\nto underlying environment mismatched configurations.",[64,92,94],{"id":93},"why-terraform-the-evaluation-decision","Why Terraform? (The Evaluation & Decision)",[34,96,97],{},"We chose Terraform for the following core reasons:",[99,100,101,105,108,111],"ol",{},[102,103,104],"li",{},"It's capability to manage resources with cloud-agnostic flexibility.",[102,106,107],{},"Defining the expected end state in a declarative configuration code instead\nof imperative scripts.",[102,109,110],{},"The power of the ecosystem with a rich module registry, active community\nsupport and broad provider support.",[102,112,113],{},"Tracking resource mappings and dependencies through a state file which\nprovides increased idempotency.",[34,115,116,117,122,123,127,128,131,132,131,135,138],{},"We use Terraform to provision and manage infrastructure across diverse\nenvironments, including Microsoft Azure, ",[41,118,121],{"href":119,"rel":120},"https:\u002F\u002Fwww.vultr.com",[45],"Vultr",", etc\nusing a single, unified workflow. By standardising around the Hashicorp\nConfiguration Language (HCL) and a consistent execution lifecycle (",[124,125,126],"code",{},"init",",\n",[124,129,130],{},"plan",", ",[124,133,134],{},"apply",[124,136,137],{},"destroy","), engineers apply the same authoring, code review,\nand automation practices regardless of the underlying platform.",[34,140,141],{},"While cloud-agnostic execution doesn't make vendor-specific abstractions\nidentical, for example, Azure RBAC models remain structurally distinct from\nother providers (such as Vultr), standardising the operational layer eliminates\ncontext switching and simplifies hybrid or multi-provider architectures.",[34,143,144],{},"The other benefit of using Terraform is its reliance on HCL to provide a\ndeclarative model instead of relying on imperative scripts. Using HCL, our\nengineers define the desired end state to easily manage the infrastructure of a\nrequired project.",[34,146,147],{},"Here's a sample code snippet showcasing what Terraform's HCL code looks like:",[149,150,155],"pre",{"className":151,"code":152,"language":153,"meta":154,"style":154},"language-hcl shiki shiki-themes github-dark","terraform {\n  required_version = \">= 1.5.0\"\n\n  required_providers {\n    random = {\n      source  = \"hashicorp\u002Frandom\"\n      version = \"~> 3.6\"\n    }\n  }\n}\n\nprovider \"random\" {}\n\nvariable \"pet_length\" {\n  description = \"Number of words in the generated pet name\"\n  type        = number\n  default     = 2\n}\n\nresource \"random_pet\" \"server\" {\n  length    = var.pet_length\n  separator = \"-\"\n}\n\noutput \"server_name\" {\n  description = \"Generated name for the server\"\n  value       = random_pet.server.id\n}\n","hcl","",[124,156,157,170,184,191,199,209,221,232,238,244,250,255,268,273,284,295,307,319,324,329,343,360,371,376,381,392,402,424],{"__ignoreMap":154},[158,159,162,166],"span",{"class":160,"line":161},"line",1,[158,163,165],{"class":164},"svObZ","terraform",[158,167,169],{"class":168},"s95oV"," {\n",[158,171,173,176,180],{"class":160,"line":172},2,[158,174,175],{"class":168},"  required_version",[158,177,179],{"class":178},"snl16"," =",[158,181,183],{"class":182},"sU2Wk"," \">= 1.5.0\"\n",[158,185,187],{"class":160,"line":186},3,[158,188,190],{"emptyLinePlaceholder":189},true,"\n",[158,192,194,197],{"class":160,"line":193},4,[158,195,196],{"class":164},"  required_providers",[158,198,169],{"class":168},[158,200,202,205,207],{"class":160,"line":201},5,[158,203,204],{"class":168},"    random",[158,206,179],{"class":178},[158,208,169],{"class":168},[158,210,212,215,218],{"class":160,"line":211},6,[158,213,214],{"class":168},"      source  ",[158,216,217],{"class":178},"=",[158,219,220],{"class":182}," \"hashicorp\u002Frandom\"\n",[158,222,224,227,229],{"class":160,"line":223},7,[158,225,226],{"class":168},"      version ",[158,228,217],{"class":178},[158,230,231],{"class":182}," \"~> 3.6\"\n",[158,233,235],{"class":160,"line":234},8,[158,236,237],{"class":168},"    }\n",[158,239,241],{"class":160,"line":240},9,[158,242,243],{"class":168},"  }\n",[158,245,247],{"class":160,"line":246},10,[158,248,249],{"class":168},"}\n",[158,251,253],{"class":160,"line":252},11,[158,254,190],{"emptyLinePlaceholder":189},[158,256,258,261,265],{"class":160,"line":257},12,[158,259,260],{"class":164},"provider",[158,262,264],{"class":263},"sDLfK"," \"random\"",[158,266,267],{"class":168}," {}\n",[158,269,271],{"class":160,"line":270},13,[158,272,190],{"emptyLinePlaceholder":189},[158,274,276,279,282],{"class":160,"line":275},14,[158,277,278],{"class":164},"variable",[158,280,281],{"class":263}," \"pet_length\"",[158,283,169],{"class":168},[158,285,287,290,292],{"class":160,"line":286},15,[158,288,289],{"class":168},"  description",[158,291,179],{"class":178},[158,293,294],{"class":182}," \"Number of words in the generated pet name\"\n",[158,296,298,301,304],{"class":160,"line":297},16,[158,299,300],{"class":168},"  type",[158,302,303],{"class":178},"        =",[158,305,306],{"class":178}," number\n",[158,308,310,313,316],{"class":160,"line":309},17,[158,311,312],{"class":168},"  default",[158,314,315],{"class":178},"     =",[158,317,318],{"class":263}," 2\n",[158,320,322],{"class":160,"line":321},18,[158,323,249],{"class":168},[158,325,327],{"class":160,"line":326},19,[158,328,190],{"emptyLinePlaceholder":189},[158,330,332,335,338,341],{"class":160,"line":331},20,[158,333,334],{"class":164},"resource",[158,336,337],{"class":263}," \"random_pet\"",[158,339,340],{"class":263}," \"server\"",[158,342,169],{"class":168},[158,344,346,349,352,355,357],{"class":160,"line":345},21,[158,347,348],{"class":168},"  length",[158,350,351],{"class":178},"    =",[158,353,354],{"class":168}," var",[158,356,78],{"class":178},[158,358,359],{"class":168},"pet_length\n",[158,361,363,366,368],{"class":160,"line":362},22,[158,364,365],{"class":168},"  separator",[158,367,179],{"class":178},[158,369,370],{"class":182}," \"-\"\n",[158,372,374],{"class":160,"line":373},23,[158,375,249],{"class":168},[158,377,379],{"class":160,"line":378},24,[158,380,190],{"emptyLinePlaceholder":189},[158,382,384,387,390],{"class":160,"line":383},25,[158,385,386],{"class":164},"output",[158,388,389],{"class":263}," \"server_name\"",[158,391,169],{"class":168},[158,393,395,397,399],{"class":160,"line":394},26,[158,396,289],{"class":168},[158,398,179],{"class":178},[158,400,401],{"class":182}," \"Generated name for the server\"\n",[158,403,405,408,411,414,416,419,421],{"class":160,"line":404},27,[158,406,407],{"class":168},"  value",[158,409,410],{"class":178},"       =",[158,412,413],{"class":168}," random_pet",[158,415,78],{"class":178},[158,417,418],{"class":168},"server",[158,420,78],{"class":178},[158,422,423],{"class":168},"id\n",[158,425,427],{"class":160,"line":426},28,[158,428,249],{"class":168},[34,430,431,432,435,436,439,440,443],{},"You can save the code snippets shared above in a ",[124,433,434],{},"main.tf"," file then run\n",[124,437,438],{},"terraform plan -out=\"main.tfplan\""," to build the plan. The plan can then safely\nconsumed by Terraform's ",[124,441,442],{},"terraform apply \"main.tfplan\""," command to actually\nprovision the infrastructure.",[34,445,446,447,451],{},"During execution, Terraform compares the target configuration against existing\ninfrastructure to compute a deterministic execution plan, safely creating,\nupdating or destroying resources to converge on the expected state. This\napproach deliver idempotent deployments, makes infrastructure drift detectable,\nand allows our engineers to inspect exact resource diffs during PR reviews\nbefore any live changes occur. You want to read\n",[41,448,450],{"href":449},"\u002Fblog\u002Ftaking-terraform-to-production","Taking Terraform to Production: Automating IaC with CI\u002FCD","\nto learn more about our automated workflows.",[34,453,454,455,460],{},"The ",[41,456,459],{"href":457,"rel":458},"https:\u002F\u002Fregistry.terraform.io",[45],"Terraform Registry"," provides our teams\naccess to a wide range of public and private (internal) module repositories as\nwell. The contents of these repositories encapsulate hardened and reusable\narchitectural patterns such as VPC topologies, cluster baselines, and IAM\nguardrails behind standardised input interfaces. Backed by industry adoption,\nthis ecosystem also provides well-established CI\u002FCD patterns, static analysis\ntools and policy-as-code integrations. All these factors are a major deciding\nfactor for us to end up using Terraform as our preferred tool for managing our\ncloud infrastructure.",[34,462,463,464,467],{},"Lastly, at the core of Terraform's execution engine is its state file (usually\nnamed ",[124,465,466],{},"terraform.tfstate","), which maintains a persistent mapping between\nresource definitions in HCL and real-world provisioned objects. The state tracks\nresource identifiers, metadata, and implicit or explicit dependency graphs so\nTerraform can determine the exact order in which changes must be applied and\navoid querying every provider API exhaustively on each run.",[34,469,470],{},"On a side note it should be also noted, this state file serves as the\nauthoritative record of managed infrastructure and often contains sensitive\nattributes. For our production requirements we store this state file in a\nremote, encrypted backend, such as Microsoft's Azure Blob Storage but for local\ntesting environments, saving it locally is probably fine as well.",[34,472,473],{},"Here's how we store the state file in a remote (Azure) backend:",[149,475,477],{"className":151,"code":476,"language":153,"meta":154,"style":154},"terraform {\n  required_version = \">= 1.5.0\"\n\n  backend \"azurerm\" {\n    resource_group_name  = \"rg-terraform-state\"\n    storage_account_name = \"sttfstateprod001\" # Must be globally unique across Azure\n    container_name       = \"tfstate\"\n    key                  = \"networking\u002Fprod.terraform.tfstate\"\n\n    # Recommended: authenticate via Microsoft Entra ID (e.g., OIDC in pipelines or Azure CLI locally)\n    # Ensure the identity has the \"Storage Blob Data Contributor\" role on the storage account\u002Fcontainer\n    use_azuread_auth = true\n  }\n}\n",[124,478,479,485,493,497,507,518,532,542,553,557,562,567,577,581],{"__ignoreMap":154},[158,480,481,483],{"class":160,"line":161},[158,482,165],{"class":164},[158,484,169],{"class":168},[158,486,487,489,491],{"class":160,"line":172},[158,488,175],{"class":168},[158,490,179],{"class":178},[158,492,183],{"class":182},[158,494,495],{"class":160,"line":186},[158,496,190],{"emptyLinePlaceholder":189},[158,498,499,502,505],{"class":160,"line":193},[158,500,501],{"class":164},"  backend",[158,503,504],{"class":263}," \"azurerm\"",[158,506,169],{"class":168},[158,508,509,512,515],{"class":160,"line":201},[158,510,511],{"class":168},"    resource_group_name",[158,513,514],{"class":178},"  =",[158,516,517],{"class":182}," \"rg-terraform-state\"\n",[158,519,520,523,525,528],{"class":160,"line":211},[158,521,522],{"class":168},"    storage_account_name",[158,524,179],{"class":178},[158,526,527],{"class":182}," \"sttfstateprod001\"",[158,529,531],{"class":530},"sAwPA"," # Must be globally unique across Azure\n",[158,533,534,537,539],{"class":160,"line":223},[158,535,536],{"class":168},"    container_name",[158,538,410],{"class":178},[158,540,541],{"class":182}," \"tfstate\"\n",[158,543,544,547,550],{"class":160,"line":234},[158,545,546],{"class":168},"    key",[158,548,549],{"class":178},"                  =",[158,551,552],{"class":182}," \"networking\u002Fprod.terraform.tfstate\"\n",[158,554,555],{"class":160,"line":240},[158,556,190],{"emptyLinePlaceholder":189},[158,558,559],{"class":160,"line":246},[158,560,561],{"class":530},"    # Recommended: authenticate via Microsoft Entra ID (e.g., OIDC in pipelines or Azure CLI locally)\n",[158,563,564],{"class":160,"line":252},[158,565,566],{"class":530},"    # Ensure the identity has the \"Storage Blob Data Contributor\" role on the storage account\u002Fcontainer\n",[158,568,569,572,574],{"class":160,"line":257},[158,570,571],{"class":168},"    use_azuread_auth",[158,573,179],{"class":178},[158,575,576],{"class":263}," true\n",[158,578,579],{"class":160,"line":270},[158,580,243],{"class":168},[158,582,583],{"class":160,"line":275},[158,584,249],{"class":168},[34,586,587],{},"To further prevent concurrent modifications and state corruption, we also enable\nstate locking and use automated CI\u002FCD workflows to manage the infrastructure.",[64,589,591],{"id":590},"the-impact-long-term-benefits","The Impact & Long-Term Benefits",[34,593,594],{},"Ever since we standardised our workflows and infrastructure management around\nTerraform, we noticed measurable operational velocity, stronger governance and\nhigher developer autonomy. We no longer have to deal with reactive firefighting\nand manual bottlenecks. Instead we're more focused towards deployment that scale\nalongside our product delivery requirements.",[34,596,597],{},"Here are some ways how using Terraform and a standardised approach to manage our\ninfrastructure has helped us:",[599,600,601,604,607],"ul",{},[102,602,603],{},"The automated environment and resource provisioning compresses delivery cycles\nfrom days or hours of manual ticket queues and console configuration down to\nminutes of repeatable execution. We now spin up\u002Fdown ephemeral test\nenvironments, staging stacks, and production resources on demand with\nconsistent configurations, removing setup delays from feature development and\nrelease schedules.",[102,605,606],{},"Embedding security and governance checks directly in to PRs and CI\u002FCD\npipelines shift compliance leftwards. We now catch misconfigurations before\nresources are ever provisioned rather than discovering them during periodic\naudits. Our engineers now enforce encryption at rest with least-privilege\naccess patterns, network segmentation, and required tagging standards\nautomatically in code, producing a continuous, auditable trail of policy\nadherence.",[102,608,609],{},"We also maintain private (internal) and some public shared modules with\nautomatic validation and clear guardrails which allow our product engineers to\nprovision and manage routine infrastructure independently. They no longer have\nto file tickets for every minor adjustment. This allows our DevOps Engineers\nto stay focused on shared foundations, reliability, and complex architectural\nproblems, while developers ship faster with confidence of their changes\nstaying within safe organisational boundaries.",[64,611,613],{"id":612},"lessons-learned-advice-for-others","Lessons Learned & Advice for Others",[34,615,616],{},"Looking back on our journey with Terraform, some of the most valuable takeaways\ncame not from syntax or tooling, but how we paced our adoption and protected our\noperational foundations. If you're preparing to introduce Terraform to your team\nor company, here are a few practical lessons which will help you stand out:",[99,618,619,626,629],{},[102,620,621,622,625],{},"Don't cheap out or take shortcuts when securing the state file to avoid\ncostly incidents down the line. We made a decision early on to treat our\nremote state backend with the same level of security and rigor as a\nproduction database.",[623,624],"br",{},"Even to this day, we store our Terraform state file remotely with strict\nrole-based access control, encryption at rest, versioning, and automated\nstate locking to ensure sensitive metadata stays protected. Establishing such\ndiscipline for day one saved us from the kind of state corruption headaches\nwhich might potentially stall an entire engineering team otherwise.",[102,627,628],{},"When starting out, it can be tempting to try importing and codifying your\nentire legacy footprint all at once. In our experience, this approach creates\nan unnecessary risk and slows down momentum. Instead we recommend starting\nout with a greenfield service or a low-risk, non-critical workload. This\nshould give your team\u002Fcompany room to establish repository conventions, test\nmodule patterns and refine your CI\u002FCD workflows before bringing\nmission-critical production infrastructure under Terraform management.",[102,630,631,632,635,636,638],{},"Like any meaningful shift in engineering workflows, adopting Terraform comes\nwith a real learning curve (we say so from our own experiences). Whether it\nwas resolving a stubborn state lock, refactoring early configurations which\ngrew too monolithic, or learning when to reach for ",[124,633,634],{},"moved"," blocks instead of\nletting Terraform destroy and recreate a resource, each mistake sharpened our\nunderstanding of how the tool behaves under the hood.",[623,637],{},"Treating these early friction points as part of the learning process is\nultimately what turned Terraform from a new tool into a dependable foundation\nwe trust in production.",[640,641,642],"style",{},"html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .s95oV, html code.shiki .s95oV{--shiki-default:#E1E4E8}html pre.shiki code .snl16, html code.shiki .snl16{--shiki-default:#F97583}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}",{"title":154,"searchDepth":172,"depth":172,"links":644},[645,646,647,648],{"id":66,"depth":172,"text":67},{"id":93,"depth":172,"text":94},{"id":590,"depth":172,"text":591},{"id":612,"depth":172,"text":613},"infrastructure","\u002Fblog\u002Fstandardised-terraform-practices.webp","2026-11-19","Discover how we standardized our cloud infrastructure on Terraform. Learn how Infrastructure as Code (IaC) eliminated drift, accelerated deployments, and scaled our workflows.","md",{},"\u002Fblog\u002Fstandardised-terraform-practices",{"title":28,"description":652},"blog\u002Fstandardised-terraform-practices","iXOpU0L3aCBY4HeQuTBEoNvSIXUacf_jlIvbGrGu6aU",[660,666],{"title":661,"path":662,"stem":663,"description":664,"date":665,"children":-1},"Securely Self-Hosting PostgreSQL: Configuration, Backups, and Best Practices","\u002Fblog\u002Fsecurely-self-hosting-postgresql","blog\u002Fsecurely-self-hosting-postgresql","Take full control of your data by setting up your own self-hosted PostgreSQL database. Discover how to configure, secure, and manage production-ready instances efficiently.","2026-08-10",{"title":450,"path":449,"stem":667,"description":668,"date":669,"children":-1},"blog\u002Ftaking-terraform-to-production","Learn how to automate Terraform with CI\u002FCD pipelines. Discover OIDC authentication, automated PR plans, state locking, and drift detection for production IaC.","2026-11-02",[671,673,677,681,684,685],{"path":449,"title":450,"date":669,"category":672},"Infrastructure",{"path":674,"title":675,"date":676,"category":672},"\u002Fblog\u002Fautomated-restic-backups","How We Automated Secure, Deduplicated Backups with Restic","2026-09-29",{"path":678,"title":679,"date":680,"category":672},"\u002Fblog\u002Fgolden-images-with-packer","Golden Images at Scale: Building Secure, Multi-Cloud VMs with Packer","2026-09-11",{"path":76,"title":682,"date":683,"category":672},"Managing Infrastructure Drift: How Packer, Terraform, and Ansible Keep Enterprise Environments Compliant","2026-09-03",{"path":662,"title":661,"date":665,"category":672},{"path":686,"title":687,"date":688,"category":689},"\u002Fblog\u002Fhello-world","Hello, world","2026-05-22","People",1795174673817]