Option for CloudShell to Kill and Rebuild Shell venvs

Hi Kimo, Thanks for the idea, Looking forward for the votes.

Hi @ksaper@tsieda.com

Regarding the last comment, please note that restarting the execution server cleans the venv folder.

http://help.quali.com/Online%20Help/8.3/Portal/Content/Admn/Cnfgr-Pyth-Env-Cleanup.htm

Yaniv

Yes, you can restart said Server (the whole server not just the service) - but I can't administratively trigger that action from CloudShell's portal. And there is also the assumption that the only critical thing running on there is Quali's Execution Server. I may have other services or applications running on that Server, which also happens to be running Quali's Execution Server. If I need to update a vnev because of a backend package push, and I have other things running there, I now have to schedule downtime or otherwise notify about an outage to reboot that machine.

I've ran the configuration tool and that doesn't remove them. Nor does restarting the TestShell Execution Service from the Task Manager.

I also did test the "Restart the host machine" on my Installation (Windows 10) and all the same venv were there after the restart. I've provided feedback directly to help on this point.

I also know the alternative is to go in and kill the specific venv by deleting it - again not an easy administrative task. And that's not what the documentation says to do.

I'll open a ticket on this specifically. But the ability to request from the CloudShell portal to Rebuild that Shell or Script should be an option (and would ensure that the system finds all instances of it)

Also, the clean up removes Unused venv. So I have an active shell or script with a venv (currently in inventory per se) but there is a update to a supporting library, then there is no listed method for getting that venv to re-build w/out reloading the item, or deleting the venv.