ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Goal: use Terraform moved block to rename a resource while also updating its arguments (e.g., tags) without triggering a delete‑create replace that could cause downtime. Constraint: the moved block guarantees a move action only when the resource type and provider stay the same and no ID‑changing arguments are modified; however, Terraform’s documentation does
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
Goal Ensure that Terraform retries a provider operation after a transient error without creating duplicate resources when the underlying API call is not idempotent. Constraints and uncertainty Providers can mark individual CRUD actions as retryable via the SDK’s Retryable field, which assumes the provider implements idempotency for those actions. If an actio
Implementing least-privilege access in Terraform often involves using short-lived credentials via OIDC or IAM roles to minimize the risk of long-lived secret leakage. While this architecture reduces the blast radius of a compromise, it introduces dependencies on the credential lifecycle during long-running operations. There is uncertainty regarding how diffe
I want to create service principal with terraform and have written terraform script for that. I have Azure DevOps pipelone in which I ma running this pipeline. Service principal which I am using to run the terraform script has owner access on subscription. I am getting below error while creating azure ad application │ │ with module.appregister.azuread_applic
So azurerm updated to 2.0 a few hours ago.... My main code is version locked for safety, but I'm doing some testing to see what's changed from the public beta of 1.44 and now I'm getting this error on any TF command apart from terraform init. has anybody else come upon this?
Terraform ELB Target Group Migration with create_before_destroy The goal is to migrate a small application behind an AWS Elastic Load Balancer (ELB) target group without downtime by using Terraform's lifecycle { create_before_destroy = true } to provision a replacement target group before destroying the original. However, Terraform does not control the order
Clarifying the documented limits for count.index and count.indexes is needed for a module design that relies on count to iterate over inputs of varying types. The relevant capability is the use of count.index for list and set iterations and count.indexes for map iterations in Terraform 1.9+. The behavior is documented for collection-typed arguments, with unc
azure