databricks/devbox

devbox's Issues

Argument parsing silently drops unknown arguments

Should be easy enough to just throw an error message or something

--new-instance does not work when old instance is not running

Even with --new-instance the old instance will be reused if it's not currently running. The flag only works when the old instance is already running.

Extra newline in git output

When running git commands through the Git proxy there's an extra newline in the output.

$ git branch
  CJ-25007
  issue/PLAT-16767-error-msgs
  issue/quill-static-analysis-bug
  master
  pr/56970
* upgrade/devbox-script
  upgrade/scala-2.12.11
  upgrade/sjsonnet

Git proxy hardcoded port prevents multiple devboxes from syncing concurrently

This is the only thing that prevents concurrent use, so although multiple concurrent devboxes is a bit unusual, it should be easy enough to make the port configurable to allow multiple devboxes to sync at the same time

Setup files are owned by root

Files passed as --setup-file are run as root by the DevboxSetupAgent. This causes a problem for .databricks/cache where certificates are stored, as several scripts expect to be able to write there.

The setup script should chown the directories it creates.

Can you add a README?

File in git index but gitignored is not synced after the initial sync

If a file is in .gitignore, but still in the git index, it is synced only in the initial scan. If the file appears later, such as after a git pull, it is not synced until devbox restart.

Can you add a README?