)]}'
{"tempest/cmd/cleanup.py":[{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"07600eec10c60f4b44938f0821d0403d788e6207","unresolved":false,"context_lines":[{"line_number":14,"context_line":"# under the License."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"\"\"\""},{"line_number":17,"context_line":"Utility for cleaning up environment after a failed or interrupted Tempest"},{"line_number":18,"context_line":"run"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Runtime Arguments"}],"source_content_type":"text/x-python","patch_set":1,"id":"9a30ddce_bf8514ae","line":17,"range":{"start_line":17,"start_character":36,"end_line":17,"end_character":73},"updated":"2017-03-09 09:57:13.000000000","message":"I don\u0027t think this is correct. If Tempest is really doing a good job it will cleanup all resources, but there may still be bugs in Tempest so resources may be left around. \nIn case of failed run no resources should be left around in normal circumstances. In case of interrupted one they may.\n\nIn any case, the cleanup tool can be used regardless, if everything went fine with the run it will just do nothing.\n\nIt\u0027s a decision of the user whether to include a cleanup step as part of their workflow or not.","commit_id":"3238e2f3f745a01fe218fd1ec782f371f6bd6bb3"}]}