In v1.14.0 the default value for bundle.engine will be set to direct. This will trigger automatic migration to direct engine post deployment.
In case of any errors during migration, the bundle will remain on terraform engine.
To opt out of automatic migration, you can set bundle.engine: terraform in your databricks.yml. This can also be set per target: engine: terraform.
The env var DATABRICKS_BUNDLE_ENGINE is also consulted if nothing is set in the config.
It is recommended to migrate earlier, set the engine to "direct" now to do so.
Note, support for terraform deployment engine in DABs will be deprecated in September, so in some future version of the CLI, bundles setting engine: terraform will stop working until that setting is removed.
https://docs.databricks.com/aws/en/dev-tools/bundles/direct
In v1.14.0 the default value for bundle.engine will be set to
direct. This will trigger automatic migration to direct engine post deployment.In case of any errors during migration, the bundle will remain on terraform engine.
To opt out of automatic migration, you can set
bundle.engine: terraformin your databricks.yml. This can also be set per target:engine: terraform.The env var
DATABRICKS_BUNDLE_ENGINEis also consulted if nothing is set in the config.It is recommended to migrate earlier, set the engine to "direct" now to do so.
Note, support for terraform deployment engine in DABs will be deprecated in September, so in some future version of the CLI, bundles setting
engine: terraformwill stop working until that setting is removed.https://docs.databricks.com/aws/en/dev-tools/bundles/direct