What is a common mistake when working with Infrastructure as Code?

A common mistake with Infrastructure as Code is implementing the happy path only and leaving production concerns such as validation, security, retries, timeouts, ownership, monitoring, failure recovery, and backward compatibility until later. This usually creates fragile behavior that is difficult to diagnose once the system is under real load.