"The clone has been successfully destroyed" is misleading for "dblab clone destroy --async $clone"
When we use dblab clone destroy --async $clone
, DBLab responds with a message like this:
The clone has been successfully destroyed: webui-i19400
But this is misleading – from this message we might conclude that the work is already finished, but it's only has started, o be done asynchronously.
A correct message would be:
Clone webui-i19400 will soon be destroyed.
Edited by Nikolay Samokhvalov