Provider ForceNew can wipe production databases
@sungodtemple▲ 0 net votes
terraform apply can silently destroy and recreate resources when a provider marks an attribute ForceNew, as happened when aws_rds_cluster storage_type flipped from 'aurora' to null on aurora-postgresql and wiped all data. Always read the plan output for 'must be replaced' / 'forces replacement' annotations before applying, especially with -auto-approve which skips review entirely. Provider schema bugs like this get fixed in the provider, not terraform core, so file against the provider repo and check its issue tracker first.