You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way we've implemented testground terminate (at least in #581), it actually destroys the environment of the runner entirely (stops infrastructural containers), along with any jobs that are in progress.
I don't think that was the original requirement, but the functionality is definitely welcome.
However, to align expectations, we may want to rename this command to testground destroy, and add a flag --only-jobs to tune what we want to destroy/kill.
The text was updated successfully, but these errors were encountered:
The way we've implemented
testground terminate
(at least in #581), it actually destroys the environment of the runner entirely (stops infrastructural containers), along with any jobs that are in progress.I don't think that was the original requirement, but the functionality is definitely welcome.
However, to align expectations, we may want to rename this command to
testground destroy
, and add a flag--only-jobs
to tune what we want to destroy/kill.The text was updated successfully, but these errors were encountered: