Closed mmrose closed 6 years ago
I defined a destroy trigger like this:
config.trigger.before :destroy, :stdout => true, :stderr => true do run_remote "/vagrant/cleanup.sh" end
This leads to cleanup.sh being called right before confirmation.
cleanup.sh
Do you see any way to get the trigger called only if confirmation is given or --force is used?
--force
How do I understand this bug is not resolved?
I defined a destroy trigger like this:
This leads to
cleanup.sh
being called right before confirmation.Do you see any way to get the trigger called only if confirmation is given or
--force
is used?