Implement the new cleanup step#3904
Conversation
|
@AthreyVinay, @vaibhavdaren, although this one is a bit longer, I think it might be worth if you review this pull request as it goes through the whole step implemtation and touches all relevant places. It could give you some good insight of how the step implementation, schema handling, command line options and docs generation works. |
martinhoyer
left a comment
There was a problem hiding this comment.
Awesome!
Took me some time to understand tbh, and am trying to come up with any feedback, but got nothing. Tested it briefly, with virtual provisioning and as a user, I very much appreciate, going forward, not accumulating 50 tmt VMs to clean manually from time to time :)
The "relationship" with tmt clean cli also seems logical.
fwiw, I like it very much, but am not 100% confident around these parts of code, so my review have a somewhat limited value.
Shouldn't the current |
Yes, the current |
|
|
AthreyVinay
left a comment
There was a problem hiding this comment.
Thanks @psss for looping me in, looks great, and yeah, definitely a solid way to get familiar with the different aspects.
The `tmt try` command needs to be updated as well to include the new `cleanup` command. Without this change provisioned guests would not be stopped and removed upon quit from the `tmt try` session. Related: #3904
Introduce a separate
cleanupstep to handle guest cleanup and workdir pruning so that thefinishstep can be reserved for user finishing tasks only without having to always stop and remove guests.Fix #1737.
Pull Request Checklist