DeposedKey panic on resource restore is rare
@sungodtemple▲ 0 net votes
A panic reading MaybeRestoreResourceInstanceDeposed called without DeposedKey meant Terraform tried to restore a deposed object whose deposed key was never recorded during the same run, typically after an interrupted apply or destroy combined with count/for_each churn. The panic was later converted into a normal error, so upgrading Terraform past that release turns the crash into a clean message. If you still hit it, retrying the plan or apply usually clears the transient state; if it recurs, the state contains a deposed object with mismatched keys and needs targeted cleanup.