mirror of https://github.com/databricks/cli.git
e2db0cd0e2
## Changes - Instead of constructing chains of mutators and then executing them, execute them directly. - Remove functionality related to chain-building: Seq, If, Defer, newPhase, logString. - Phases become functions that apply the changes directly rather than construct mutator chains that will be called later. - Add a helper ApplySeq to call multiple mutators, use it where Apply+Seq were used before. This is intended to be a refactoring without functional changes, but there are a few behaviour changes: - Since defer() is used to call unlock instead of bundle.Defer() unlocking will now happen even in case of panics. - In --debug, the phase names are are still logged once before start of the phase but each entry no longer has 'seq' or phase name in it. - The message "Deployment complete!" was printed even if terraform.Apply() mutator had an error. It no longer does that. ## Motivation The use of the chains was necessary when mutators were returning a list of other mutators instead of calling them directly. But that has since been removed, so now the chain machinery have no purpose anymore. Use of direct functions simplifies the logic and makes bugs more apparent and easy to fix. Other improvements that this unlocks: - Simpler stacktraces/debugging (breakpoints). - Use of functions with narrowly scoped API: instead of mutators that receive full bundle config, we can use focused functions that only deal with sections they care about prepareGitSettings(currentGitSection) -> updatedGitSection. This makes the data flow more apparent. - Parallel computations across mutators (within phase): launch goroutines fetching data from APIs at the beggining, process them once they are ready. ## Tests Existing tests. |
||
|---|---|---|
| .. | ||
| assumptions | ||
| bundle | ||
| cmd | ||
| internal/acc | ||
| libs | ||
| python | ||
| README.md | ||
README.md
Integration tests
This directory contains integration tests for the project.
The tree structure generally mirrors the source code tree structure.
Requirements for new files in this directory:
- Every package must be named after its directory with
_testappended- Requiring a different package name for integration tests avoids aliasing with the main package.
- Every integration test package must include a
main_test.gofile.
These requirements are enforced by a unit test in this directory.
Running integration tests
Integration tests require the following environment variables:
CLOUD_ENV- set to the cloud environment to use (e.g.aws,azure,gcp)DATABRICKS_HOST- set to the Databricks workspace to useDATABRICKS_TOKEN- set to the Databricks token to use
Optional environment variables:
TEST_DEFAULT_WAREHOUSE_ID- set to the default warehouse ID to useTEST_METASTORE_ID- set to the metastore ID to useTEST_INSTANCE_POOL_ID- set to the instance pool ID to useTEST_BRICKS_CLUSTER_ID- set to the cluster ID to use
To run all integration tests, use the following command:
go test ./integration/...
Alternatively:
make integration