bundle deploy/destroy: report per-resource actions and a summary (#5720)

`bundle deploy` now lists the per-resource actions and summary lines,
instead of generic progress chatter:

```
Uploading bundle files to /Workspace/Users/me@example.com/.bundle/my_project/dev/files...
Created jobs.my_job
Created jobs.no_tasks_job
Files: 7 uploaded, 0 deleted
Resources: 2 created, 0 changed, 0 deleted, 0 unchanged
```

`Files:` is reported separately because a deploy that only changes
business logic (a `.py` or `.sql` file) leaves every resource unchanged,
so a lone `0 changed` reads like a no-op. Both lines always print, so
the shape of the output does not vary between deploys.

A deploy that fails after uploading still reports `Files:` — those files
were uploaded. It does not report `Resources:`, which would describe
what was intended rather than what was applied.

`bundle destroy` gets a matching summary line (`Destroy: N deleted`),
counting top-level resources to match its approval list.

## Details
- Add `CountActions()`/`ActionCounts` and `NotSelected` to
`deployplan.Plan`.
- `libs/sync` retains the upload/delete counts from its diff; `b.Files`
lists every tracked file, not the changed ones.
- `-q`/`--quiet` prints only the summary lines. Repeat it (`-qq`) to
print only warnings and errors, which also drops progress messages
(`Uploading bundle files to ...`, `Building ...`, `Executing
'postdeploy' script`). Supported on `plan`, `deploy`, `destroy` and
`pipelines deploy`; `destroy` did not have `-q` before. It is a repeat
counter, and progress suppression travels on the context
(`cmdio.WithQuiet`/`LogProgress`) because those messages come from
mutators that receive no bundle. `acceptance/bundle/quiet-levels` covers
all nine command/level combinations; acceptance tests use `-qq` where
the engines genuinely diverge per-resource.
- With `--select`, the resource summary appends `, N not selected`.
- Drop progress chatter: `Deploying resources...`, `Deployment
complete!`, `Updating deployment state...`, `Deleting files...`,
`Destroy complete!`.
- The summary prints after the `postdeploy` script, so a failing script
is not preceded by a line that appears to vouch for the run; it still
prints on that failure (the resources were applied) and the script's
error still propagates.

Author: denik

.nextchanges/notable-changes/deploy-summary.md

@@ -0,0 +1 @@
+* `bundle deploy` now reports the per-resource actions it took, how many files it synced, and a summary of created/changed/deleted/unchanged resources; `bundle destroy` reports how many resources it deleted. `-q` prints only the summaries, `-qq` only warnings and errors. ([#5720](https://github.com/databricks/cli/pull/5720))

acceptance/apps/deploy/bundle-no-args-with-flags/output.txt

@@ -2,9 +2,9 @@
 >>> [CLI] apps deploy --skip-validation --auto-approve --force-lock --fail-on-active-runs
 Deploying project...
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created apps.myapp
+Files: 6 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 ✓ Getting the status of the app myapp
 ✓ App is in UNAVAILABLE state
 ✓ App compute is in STOPPED state
@@ -21,5 +21,4 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/test-bundle/default
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted

acceptance/apps/deploy/bundle-no-args/output.txt

@@ -2,9 +2,9 @@
 >>> [CLI] apps deploy --skip-validation
 Deploying project...
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created apps.myapp
+Files: 6 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 ✓ Getting the status of the app myapp
 ✓ App is in UNAVAILABLE state
 ✓ App compute is in STOPPED state
@@ -21,5 +21,4 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/test-bundle/default
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted

acceptance/bundle/ai_runtime_task/local_code_source/output.txt

@@ -3,9 +3,9 @@
 
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/ai-runtime-test/default/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created jobs.train
+Files: 14 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 
 === each task's tarball holds only synced files (both under the repo root .air_snapshots)
 
@@ -110,9 +110,9 @@ Plan: 0 to add, 0 to change, 0 to delete, 1 unchanged
 
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/ai-runtime-test/default/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Updated jobs.train
+Files: 4 uploaded, 1 deleted
+Resources: 0 created, 1 changed, 0 deleted, 0 unchanged
 
 >>> print_requests.py --sort --del-field raw_body //.air_snapshots/
 {
@@ -131,5 +131,4 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/ai-runtime-test/default
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted

acceptance/bundle/apps/app_yaml/output.txt

@@ -15,9 +15,9 @@ Plan: 1 to add, 0 to change, 0 to delete, 0 unchanged
 
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created apps.myapp
+Files: 7 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 
 >>> jq select(.path | test("app.yml")) out.requests.txt
 
@@ -27,8 +27,7 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/test-bundle/default
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted
 
 >>> print_requests.py //apps
 {

acceptance/bundle/apps/compute_size/out.update.direct.txt

@@ -1,9 +1,9 @@
 
 >>> errcode [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/app-compute-size-[UNIQUE_NAME]/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Updated apps.my_app
+Files: 4 uploaded, 0 deleted
+Resources: 0 created, 1 changed, 0 deleted, 0 unchanged
 
 >>> [CLI] apps get app-[UNIQUE_NAME]
 {

acceptance/bundle/apps/compute_size/out.update.terraform.txt

@@ -1,7 +1,6 @@
 
 >>> errcode [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/app-compute-size-[UNIQUE_NAME]/files...
-Deploying resources...
 Error: terraform apply: exit status 1
 
 Error: failed to update app
@@ -14,7 +13,7 @@ Compute size updates are not supported in this update API. Please use the new
 update API instead.
 
 
-Updating deployment state...
+Files: 4 uploaded, 0 deleted
 
 Exit code: 1
 

acceptance/bundle/apps/compute_size/output.txt

@@ -2,9 +2,9 @@
 === Deploy bundle
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/app-compute-size-[UNIQUE_NAME]/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created apps.my_app
+Files: 8 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 
 === Update compute size and redeploy
 >>> [CLI] bundle destroy --auto-approve
@@ -13,5 +13,4 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/app-compute-size-[UNIQUE_NAME]
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted

acceptance/bundle/apps/git_source/output.txt

@@ -18,9 +18,9 @@ Plan: 1 to add, 0 to change, 0 to delete, 0 unchanged
 === Deploy bundle
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/app-git-source-[UNIQUE_NAME]/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Created apps.my_app
+Files: 8 uploaded, 0 deleted
+Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
 
 >>> [CLI] bundle run my_app
 ✓ Getting the status of the app [APP_NAME]
@@ -61,9 +61,8 @@ You can access the app at [APP_NAME]-123.cloud.databricksapps.com
 === Update git_source branch and redeploy
 >>> [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/app-git-source-[UNIQUE_NAME]/files...
-Deploying resources...
-Updating deployment state...
-Deployment complete!
+Files: 5 uploaded, 0 deleted
+Resources: 0 created, 0 changed, 0 deleted, 1 unchanged
 
 === Verify config update was applied
 >>> [CLI] apps get [APP_NAME] --output json
@@ -78,5 +77,4 @@ The following resources will be deleted:
 
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/app-git-source-[UNIQUE_NAME]
 
-Deleting files...
-Destroy complete!
+Destroy: 1 deleted

acceptance/bundle/apps/job_permissions/databricks.yml.tmpl

@@ -1,6 +1,15 @@
 bundle:
   name: test-bundle-$UNIQUE_NAME
 
+# This test deploys several times and reports how many files each deploy uploaded, so
+# nothing written between the deploys may end up in the synced tree: the script's own
+# out.after_first_deploy.*, and the test runner's output.txt / ACC_REPLS, which it keeps
+# appending to while the deploy runs.
+sync:
+  exclude:
+    - out*
+    - ACC_REPLS
+
 permissions:
   - level: CAN_MANAGE
     user_name: ${workspace.current_user.userName}