mirror of https://github.com/databricks/cli.git
a27c24a397
## Changes DLT pipeline recreations are destructive. They can lead to lost history of previous updates, outage of the tables temporarily and are potentially computationally expensive. Thus we make a breaking change where a prompt is shown to the user if there configuration changes will lead to a DLT recreation. Users can skip the prompt by specifying the `--auto-approve` flag. This PR also fixes an issue with our test runner where logs from the cmdio.Logger would not get propagated to the reader returned by our cobra test runner. ## Tests Manually, and new unit and integration tests. ``` ➜ bundle-playground-3 cli bundle deploy Uploading bundle files to /Users/63ec021d-b0c6-49c0-93a0-5123953a1cb2/.bundle/test/development/files... The following DLT pipelines will be recreated. Underlying tables will be unavailable for a transient period until the newly recreated pipelines are run once successfully. History of previous pipeline update runs will be lost because of recreation: recreate pipeline foo Would you like to proceed? [y/n]: n Deployment cancelled! ``` |
||
|---|---|---|
| .. | ||
| basic | ||
| deploy_then_remove_resources | ||
| empty_bundle | ||
| job_metadata | ||
| python_wheel_task | ||
| python_wheel_task_with_environments | ||
| recreate_pipeline | ||
| spark_jar_task | ||
| uc_schema | ||
| with_includes | ||