ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
When 'terramate run --changed' skips stacks that should have changed (or flags ones that shouldn't), the cause is usually git state — shallow clones, wrong base branches, or undeclared module relationships. A diagnostic guide with ordered checks and fixes.
Three supported ways to share values between Terraform configurations — remote state, provider data sources, and variables — compared on coupling, access, and failure modes, with a working example.
Learn how Terraform state locking prevents concurrent modifications, how to set it up with AWS S3 and DynamoDB, and when to safely use force-unlock.
Stop copying and pasting HCL across environments. Learn how Terramate's Stack abstractions separate infrastructure intent from implementation to scale Terraform deployments.
Orchestrating Multi-Stack Dependencies Terramate functions as an orchestration layer that generates Terraform-compatible files from templates defined in terramate.tm.hcl . When managing a complex infrastructure hierarchy, a common requirement is the propagation of output values from a base networking stack to multiple downstream application stacks. Integrati
I have a service principal in one tenant that needs access to an Azure Container Registry in another tenant. However, I am not sure as to how to create the azurerm_role_assignment for the same. Is there a way to configure the service principal as multi-tenant such that it can have role assignments in both the tenants accordingly?
I have a tf script for provisioning a Cloud SQL instance, along with a couple of dbs and an admin user. I have renamed the instance, hence a new instance was created but terraform is encountering issues when it comes to deleting the old one. Error: Error, failed to delete instance because deletion_protection is set to true. Set it to false to proceed with in
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
I am using terraform version 0.11.13, and this afternoon I am getting the following error in terraform init step Does it mean I've to upgrade the terraform version, is there a deprecation for this version for aws provider? Full logs: Successfully configured the backend "s3"! Terraform will automatically use this backend unless the backend configuration chang
git
terramate
azure
