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 destroy.yml of the EC2 driver uses a wrong execution order. The tasks Write Molecule instance configs will immediately change the condition of the block. As soon as variable is cleaned all remaining tasks of the block will be skipped regardless of their when conditions. The cleanup tasks of for ephemeral security groups and keys will be skipped and the resources will stay.
Solution
Moving the tasks Write Molecule instance configs to the end of the destroy block. With that all destroy tasks will be executed and resources will be wiped.
The text was updated successfully, but these errors were encountered:
Problem
The
destroy.yml
of the EC2 driver uses a wrong execution order. The tasksWrite Molecule instance configs
will immediately change the condition of the block. As soon as variable is cleaned all remaining tasks of the block will be skipped regardless of their when conditions. The cleanup tasks of for ephemeral security groups and keys will be skipped and the resources will stay.Solution
Moving the tasks
Write Molecule instance configs
to the end of the destroy block. With that all destroy tasks will be executed and resources will be wiped.The text was updated successfully, but these errors were encountered: