databricks-cli/libs/sync
shreyas-goenka 715a4dfb21
Path escape filepaths in the URL (#250)
Before we were using url query escaping to escape the file path. This is
wrong since the file path is a part of the URL path rather than URL
query. These encoding schemes are similar but do not have identical
encodings which was why we got these weird edge cases

Fixed, and added nightly test for assert for this

```
2023/03/15 16:07:50 [INFO] Action: PUT: .gitignore, a b/bar.py, c+d/uno.py, foo.py
2023/03/15 16:07:51 [INFO] Uploaded foo.py
2023/03/15 16:07:51 [INFO] Uploaded a b/bar.py
2023/03/15 16:07:51 [INFO] Uploaded .gitignore
2023/03/15 16:07:51 [INFO] Uploaded c+d/uno.py
2023/03/15 16:07:51 [INFO] Initial Sync Complete
```

```
[VSCODE] bricks cli path: /Users/shreyas.goenka/.vscode/extensions/databricks.databricks-0.3.4-darwin-arm64/bin/bricks
[VSCODE] sync command args: sync,.,/Repos/shreyas.goenka@databricks.com/sync-fail.ide,--watch,--output,json
--------------------------------------------------------
Starting synchronization (4 files)
Uploaded .gitignore
Uploaded foo.py
Uploaded c+d/uno.py
Uploaded a b/bar.py
Completed synchronization
```
2023-03-15 17:25:57 +01:00
..
repofiles Path escape filepaths in the URL (#250) 2023-03-15 17:25:57 +01:00
diff.go Add optional JSON output for sync command (#230) 2023-03-08 10:27:19 +01:00
event.go Add optional JSON output for sync command (#230) 2023-03-08 10:27:19 +01:00
event_test.go Add optional JSON output for sync command (#230) 2023-03-08 10:27:19 +01:00
path.go Allow synchronization to a directory inside a repo (#213) 2023-02-20 14:34:48 +01:00
path_test.go Allow synchronization to a directory inside a repo (#213) 2023-02-20 14:34:48 +01:00
snapshot.go Add check for file exists incase of conflicting remote names (#244) 2023-03-10 11:52:45 +01:00
snapshot_test.go Add check for file exists incase of conflicting remote names (#244) 2023-03-10 11:52:45 +01:00
sync.go Let sync return early if an error occurs (#235) 2023-03-09 13:29:05 +01:00
watchdog.go Let sync return early if an error occurs (#235) 2023-03-09 13:29:05 +01:00