|
| 1 | + |
| 2 | +=== Deploy with recording on |
| 3 | +>>> [CLI] bundle deploy |
| 4 | +Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/dms-sticky-[UNIQUE_NAME]/default/files... |
| 5 | +Created jobs.foo |
| 6 | +Files: 2 uploaded, 0 deleted |
| 7 | +Resources: 1 created, 0 changed, 0 deleted, 0 unchanged |
| 8 | + |
| 9 | +=== Drop the setting: the deployment keeps recording, so the next deploy creates version 2 |
| 10 | +>>> [CLI] bundle deploy |
| 11 | +Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/dms-sticky-[UNIQUE_NAME]/default/files... |
| 12 | +Updated jobs.foo |
| 13 | +Files: 1 uploaded, 0 deleted |
| 14 | +Resources: 0 created, 1 changed, 0 deleted, 0 unchanged |
| 15 | + |
| 16 | +>>> print_requests.py --dms //api/2.0/bundle/deployments --oneline --del-body state,resource_id |
| 17 | +{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions", "q": {"version_id": "2"}, "body": {"cli_version": "[CLI_VERSION]", "operations": [{"action_type": "OPERATION_ACTION_TYPE_UPDATE", "resource_key": "jobs.foo"}], "previous_version_id": "1", "version_type": "VERSION_TYPE_DEPLOY"}} |
| 18 | +{"method": "PATCH", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/2/operations/jobs.foo", "q": {"update_mask": "state,error_message,resource_id,status"}, "body": {"error_message": "", "sequence_id": 0, "status": "OPERATION_STATUS_SUCCEEDED"}} |
| 19 | +{"method": "POST", "path": "/api/2.0/bundle/deployments/[DEPLOYMENT_ID]/versions/2/complete", "body": {"completion_reason": "VERSION_COMPLETE_SUCCESS"}} |
| 20 | + |
| 21 | +=== Wiping the local cache does not change that: the recording state is pulled from the workspace |
| 22 | +>>> [CLI] bundle plan |
| 23 | +Plan: 0 to add, 0 to change, 0 to delete, 1 unchanged |
| 24 | + |
| 25 | +=== An explicit false still conflicts with the state |
| 26 | +>>> musterr [CLI] bundle deploy |
| 27 | +Error: deployment history setting (false) does not match the existing state (true) |
| 28 | + |
| 29 | +Update experimental.deployment_history to match the existing deployment, or run "databricks bundle destroy" to start over |
| 30 | + |
| 31 | + |
| 32 | +>>> [CLI] bundle destroy --auto-approve |
| 33 | +The following resources will be deleted: |
| 34 | + delete resources.jobs.foo |
| 35 | + |
| 36 | +All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/dms-sticky-[UNIQUE_NAME]/default |
| 37 | + |
| 38 | +Destroy: 1 deleted |
0 commit comments