This adds a CLI argument to the submit command, allowing the user to skip installing virtualenv requirements.
This is especially handy for situations where the virtualenv for a topology is already set up and the topology is getting resubmitted consecutively (e.g. for testing purposes).
This is already achievable via the install_virtualenv: false option in config.json, but I think a CLI flag that controls that behaviour is useful too.
I've only added it to the submit command, and not update_virtualenv, as it's rather counter-intuitive to want to run update_virtualenv but not install requirements.
Coverage remained the same at 48.216% when pulling 0c331168b92f656bcf4851789a9e326c8b7a1e40 on pkatseas:allow-skipping-virtualuenv-creation into 7a5aa6630b9a2476c9393af1da51bb65cbcd4e37 on Parsely:master.
This adds a CLI argument to the
submit
command, allowing the user to skip installing virtualenv requirements.This is especially handy for situations where the virtualenv for a topology is already set up and the topology is getting resubmitted consecutively (e.g. for testing purposes). This is already achievable via the
install_virtualenv: false
option inconfig.json
, but I think a CLI flag that controls that behaviour is useful too.I've only added it to the
submit
command, and notupdate_virtualenv
, as it's rather counter-intuitive to want to runupdate_virtualenv
but not install requirements.