Replies: 2 comments
-
It's for the exact step that boots the VM only. As for the rest, you are suggesting an overcomplicated API. IMHO. |
Beta Was this translation helpful? Give feedback.
-
What do you mean "delay"? The VM won't start unless you explicitly invoke the action.
There are no plans to support shutting down the VM with the new syntax. It adds more complexity and takes longer for the job to finish. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The
cpa.shis IMHO a step in the right direction, however it seems this can be cleaned up a little bit more.Currently, there is no way to delay the startup of the VM or to explicitly shutdown the VM (except for from inside the VM).
It is also somewhat unclear whether the global
sync_filesdefaults or overrides or applies tocpa.sh --sync-files.I want to suggest making every single step explicit, and nothing implicit (except for shutting down the VM if it is still running at the end of the workflow).
This would imply removing/deprecating the
sync_filessetting, and providing the following operations viacpa.sh:--startup--sync-files runner-to-vmand--sync-files vm-to-runner.bothandnoneare rather meaningless when everything is explicit.--reboot--shutdownLong-term, it might also be useful to support delaying downloading of the VM image and cleaning up the VM image after the VM is shutdown, for use cases where a lot of additional disk space might be required before or after running inside the VM.
It would be somewhat consistent to also make running commands in the VM explicit via
cpa.sh --run.Beta Was this translation helpful? Give feedback.
All reactions