databricks-cli/bundle/artifacts/whl
Lennart Kats (databricks) 875c9d2db1
Tune output of bundle deploy command (#1047)
## Changes

Update the output of the `deploy` command to be more concise and
consistent:
```
$ databricks bundle deploy
Building my_project...
Uploading my_project-0.0.1+20231207.205106-py3-none-any.whl...
Uploading bundle files to /Users/lennart.kats@databricks.com/.bundle/my_project/dev/files...
Deploying resources...
Updating deployment state...
Deployment complete!
```

This does away with the intermediate success messages, makes consistent
use of `...`, and only prints the success message at the very end after
everything is completed.

Below is the original output for comparison:

```
$ databricks bundle deploy
Detecting Python wheel project...
Found Python wheel project at /tmp/output/my_project
Building my_project...
Build succeeded
Uploading my_project-0.0.1+20231207.205134-py3-none-any.whl...
Upload succeeded
Starting upload of bundle files
Uploaded bundle files at /Users/lennart.kats@databricks.com/.bundle/my_project/dev/files!

Starting resource deployment
Resource deployment completed!
```
2023-12-21 08:00:37 +00:00
..
testdata Auto detect Python wheel packages and infer build command (#603) 2023-07-26 10:07:26 +00:00
autodetect.go Tune output of bundle deploy command (#1047) 2023-12-21 08:00:37 +00:00
autodetect_test.go Auto detect Python wheel packages and infer build command (#603) 2023-07-26 10:07:26 +00:00
build.go Tune output of bundle deploy command (#1047) 2023-12-21 08:00:37 +00:00
from_libraries.go Process only Python wheel tasks which have local libraries used (#751) 2023-09-08 11:08:21 +00:00
infer.go Do not add wheel content hash in uploaded Python wheel path (#1015) 2023-11-29 10:40:12 +00:00