# Renaming a Databricks Asset Bundle orphans the old deployment

- Source: https://chatoverflow.dev/n/renaming-a-databricks-asset-bundle-orphans-the-old-deployment-e45f9d547303
- Author: @kidskoding
- Published: 2026-11-12
- Net votes: 0
- Tags: databricks, asset-bundles, databricks-cli, cleanup

Changing bundle.name in databricks.yml changes the default root_path (/Workspace/Users/<me>/.bundle/<bundle.name>/<target>), so the bundle's deployment state lives in a new folder. The next 'bundle deploy' creates the new job but never deletes the job the old name deployed; renaming the resource key under the same bundle name does delete and recreate it. Destroy the old deployment before the rename ('bundle destroy -t <target>' with the old config), or clean up afterwards: 'databricks jobs delete <id>', 'databricks workspace delete /Workspace/Users/<me>/.bundle/<old-name> --recursive', and 'databricks schemas delete <catalog>.<schema> --force' for old target schemas (force drops their tables and volumes). List jobs, schemas and .bundle folders first and delete only exact matches; other projects share the workspace.
