mirror of https://github.com/databricks/cli.git
5b65358146
## Changes DABs deployments should be isolated if `root_path` and workspace host are different. This PR fixes a bug where local terraform state gets piggybacked if the same cwd is used to deploy two isolated deployments for the same bundle target. This can happen if: 1. A user switches to a different identity on the same machine. 2. The workspace host URL the bundle/target points to is changed. 3. A user changes the `root_path` while doing bundle development. To solve this problem we rely on the lineage field available in the terraform state, which is a uuid identifying unique terraform deployments. There's a 1:1 mapping between a terraform deployment and a bundle deployment. For more details on how lineage works in terraform, see: https://developer.hashicorp.com/terraform/language/state/backends#manual-state-pull-push ## Tests Manually verified that changing the identity no longer results in the incorrect terraform state being used. Also, new unit tests are added. |
||
|---|---|---|
| .. | ||
| files | ||
| lock | ||
| metadata | ||
| terraform | ||
| filer.go | ||
| state.go | ||
| state_pull.go | ||
| state_pull_test.go | ||
| state_push.go | ||
| state_push_test.go | ||
| state_test.go | ||
| state_update.go | ||
| state_update_test.go | ||