Release notes
Contents
CLI v3.1.1
Bug fixes
-
Don’t create an empty config file when selecting "Clean/Empty" template for a new sandbox
CLI v3.1
Improvements
-
Support
--skip-start
option forsandbox create
,project create
andproject deploy
commands
CLI v3.0
Features
-
sandbox start
starts sandbox in dev mode by default -
project test
command to executegradle test
task for a project -
sandbox copy
command for copying an existing sandbox -
threshold
option for thevacuum
command for specifying age of data to be removed -
clean
option for thesnapshot restore
command to delete indices before restoring
Improvements
-
Suggest starting a new sandbox after it’s created
-
Support short
-s
flag for specifying a sandbox for project commands -
sandbox upgrade
command will no longer ask which sandbox to upgrade when executed from inside a project’s folder -
project sandbox
command now outputs current project’s sandbox
Bug fixes
-
Removed unsupported options for
upgrade
anduninstall
commands
Upgrade notes
-
In CLI 3.x, the
sandbox start
command will start the sandbox in dev mode by default. If you want to start the sandbox in prod mode, provide the--prod
option. -
All the commands that may potentially create a new sandbox (f.ex.
sandbox create
orproject create
) will now suggest starting the new sandbox after it’s created. If such a command is used in combination with-f
(--force
) option, the sandbox will be started without prompt. This may potentially affect some scripts if the command is followed by another command which now won’t be reached because script execution will be taken over by the running sandbox.