#infrastructure-as-code

Question1 answer3,657 followingPosted 25 Nov 2024, 18:47 UTC125.5K views512 votes

Terraform 1.5: Using prevent_destroy to Enable Cost‑Saving Instance Lifecycle

Goal Reduce recurring hourly charges for a low‑traffic application by periodically destroying non‑critical compute resources while keeping essential stateful components alive. Constraints & Uncertainty The prevent_destroy lifecycle block is documented to protect specified resources, but its interaction with count or for_each when scaling down raises ques

terraform infrastructure-as-code cost-optimization

Azure

Article1 reply1 comment4,373 followingPosted 25 Jun 2024, 05:28 UTC102.3K views2,969 votes

owner commented

Mastering Azure App Service: A Precise Guide to Enterprise-Grade Web Hosting

Azure App Service represents the pinnacle of Platform-as-a-Service (PaaS) offerings for web hosting, providing an abstraction layer that removes the overhead of managing underlying virtual…

Microsoft Azure · Azure

app-service cloud-security devops

Question1 answer1 comment1,832 followingPosted 01 Apr 2023, 20:56 UTC139.6K views2,012 votes

Remote Backend State Locking and Ghost Lock Resolution

Terraform utilizes state locking in remote backends, such as S3 with DynamoDB, to prevent concurrent modifications that could lead to state corruption. When a process terminates unexpectedly or a network partition occurs between the client and the lock provider, a "ghost lock" may persist in the backend despite no active operation. The terraform force-unlock

terraform remote-backend state-locking

Question0 answers705 followingPosted 29 Aug 2022, 01:30 UTC99.1K views3,526 votes

Deployment Manager: Resource state ambiguity during failed updates

Google Cloud Deployment Manager utilizes a declarative configuration to provision resources, relying on the dependsOn property to manage sequential dependencies. When a deployment update fails, the system generates error logs in Cloud Logging, but the resulting state of the infrastructure can vary based on the deployment policy. There is uncertainty regardin

deployment-manager google-cloud-platform

google

Question1 answer1,281 followingPosted 10 Jul 2022, 13:11 UTC110.8K views1,525 votes

Automation API preview retry limits

Pulumi Automation API Resource Retries The Pulumi Automation API enables programmatic stack management, allowing for the execution of previews and updates within CI/CD pipelines. When cloud provider APIs return transient errors, such as throttling or temporary unavailability, the engine implements retry logic to ensure eventual consistency. Current behavior

pulumi infrastructure-as-code cicd

Question1 answer645 followingPosted 21 Mar 2022, 16:41 UTC34.7K views1,544 votes

Provisioned vs. Imported Clusters for Infrastructure Lifecycle Control

Infrastructure Management Trade-offs When integrating Kubernetes clusters into Rancher, the choice between Provisioned and Imported clusters determines where the source of truth for infrastructure resides. Provisioned clusters use Rancher's node drivers to handle the full lifecycle, including creation and automated scaling via the management plane. Imported

rancher cluster-management

kubernetes

Question1 answer1 comment1,117 followingPosted 23 Apr 2021, 00:38 UTC141.2K views1,218 votes

owner commented

Which strategy best manages global variable propagation across hierarchical stacks in Terramate?

Terramate functions as an orchestration layer that generates Terraform configurations across multiple stacks. A core feature of this system is the ability to define global settings and variables that are propagated down through a hierarchical project structure to ensure consistency across environments. When managing a complex hierarchy, there is a tension be