@JamesGraham that makes sense depending on the workflow that was implemented. When deploying bundles from a local clone of the repo, the tfstate will be local and (hopefully) kept intact, and then the behavior will be what you describe.

But what happens when databricks bundle is issued from inside a CI/CD pipeline on an ephemeral environment? The .tfstate in that ephemeral env will be lost at the end of the pipeline, and then, if a newer version is later deployed with changes to the bundle definition, any previously deployed resource that got removed would be abandoned in the environment instead of cleaned up.