Platform & DevOps·Infrastructure described in a file
one careless change proposed to destroy the database because everything lives in a single state, and the plan was long enough not to be read.
Apply blast radius
Also calledchange radius, state splitting
How much of your estate one apply can affect, which is decided by how the configuration and state are split. A single monolithic state is convenient and means every change is a change to everything; splitting by environment, by lifecycle and by ownership shrinks what any one mistake can reach. It also shrinks plan times, which matters more than it should, because a plan nobody reads is not a control.