Our projects CI scripts are experiencing problems because of the feature that starts the sandbox after it’s created.
It would be good to have non-interactive control over that feature since it’s causing mandatory flow of a scripted feature.
As I can see here the default behavior is to start the sandbox anyways. So having control here would be really helpful.
To sum up, my suggestion is to have a command line parameter to switch off the autostart of new sandbox.
That’s a great suggestion!
We have created a task to add a new argument to the sandbox start command. Will most likely be done and released next week.
1 Like
Thank you @ase !
One question: Will it affect the CI image script?
I mean setup_sandbox.sh
Currently it’s running without parameters.
Yes, you will have to add the new argument to your sandbox start command that you call in the script file.
This was released with CLI 3.1:
1 Like