databricks-cli

Commit Graph

Author	SHA1	Message	Date
shreyas-goenka	18dae73505	[DECO-79][DECO-165] Incremental sync with support for multiple profiles (#82 ) This PR does multiple things, which are: 1. Creates .databricks dir according to outcomes concluded in "bricks configuration principles" 2. Puts the sync snapshots into a file whose names is tagged with md5(concat(host, remote-path)) 3. Saves both host and username in the bricks snapshot for debuggability Tested manually: https://user-images.githubusercontent.com/88374338/195672267-9dd90230-570f-49b7-847f-05a5a6fd8986.mov	2022-10-19 16:22:55 +02:00
shreyas-goenka	ed56fc01cb	[DECO-68] Modify acceptance test to work with deco testing infra and represent vscode usecase (#78 ) Contains changes to make this integration test work on our GitHub actions testing env 1. use go run main.go to run bricks sync to run the latest bricks from master 2. Log the output from the bricks sync process to allow for debugging 3. removed databricks.yml and instead rely on BRICKS_ROOT and other env vars for auth and bricks sync 4. Added --persist-snapshot set to false to test full sync (same as is used in the vscode extension <img width="898" alt="Screenshot 2022-09-27 at 4 26 18 PM" src="https://user-images.githubusercontent.com/88374338/192553769-7af08ca0-b73a-4cf6-a214-8c58edc4c3e5.png"> The additional logs in the picture above are from a wip PR in deco cli that I made some changes to in order to make deco cli work with bricks : https://github.com/databricks/eng-dev-ecosystem/pull/97	2022-10-05 13:28:53 +02:00
Pieter Noordhuis	a1b6fdb2e8	Update SDK (#79 )	2022-09-27 09:58:55 -07:00
shreyas-goenka	f9b66b3536	Make `bricks sync` feature work (#48 ) Tested manually and partially by unit tests	2022-09-14 17:50:29 +02:00

4 Commits