Hi everyone,
In our organization, we are transitioning from defining Databricks jobs using the UI to managing them with asset bundles. Since asset bundles can be deployed across multiple workspacesโeach potentially having multiple targets (e.g., staging, production)โI am exploring the best way to handle versioning.
Even within the same workspace, staging and production targets may require different bundle versions. Is there a built-in way to manage versioning in Databricks asset bundles by default?
One potential workaround is to pass the version as a parameter and use it in the target.presets.name. However, this approach requires specifying the version during deployment, which adds an extra step.
Ideally, Iโd like to have the version integrated directly into the bundle itself so that itโs automatically managed and consistent across deployments.
Has anyone encountered and solved this challenge? Any suggestions or best practices would be greatly appreciated!
Thanks in advance!