Back to listCategory config Workaround partial Stage deploy Freshness persistent Scope single_lib Recurring Yes Buyer Type team
Terraform state drift from manual cloud console changes
7/10 HighTeams circumvent Terraform workflows by making changes directly in cloud provider consoles, causing state files to become out of sync with actual infrastructure. This drift prevents accurate planning and can lead to unexpected behavior during subsequent Terraform operations.
Sources
Collection History
Query: “What are the most common pain points with Terraform for developers in 2025?”3/29/2026
Managing this state file, in a codebase entirely separate from the application code, can be problematic in a large team setting – especially as individuals will often circumvent the process by making changes directly in the cloud provider's console. This often causes 'drift', meaning the configuration file does not match reality.
Created: 3/29/2026Updated: 3/29/2026