Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing Default Storage when running Kitchen Destroy #188

Closed
ghost opened this issue Aug 15, 2015 · 1 comment
Closed

Removing Default Storage when running Kitchen Destroy #188

ghost opened this issue Aug 15, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Aug 15, 2015

I am sorry if this is documented elsewhere. In my .kitchen.yml file, I am specifying EC2 instances I want to create and that works fine :) The problem is that when the instances are destroyed, the storage is left behind. I see that there is an option where I can destroy EBS backed storage if I create it but I do not have a need to.

Is there a way the storage added to an AMI by default can be deleted when the instance is destroyed?

@ghost
Copy link
Author

ghost commented Aug 15, 2015

After more testing, it appears that the AMIs I am using are setup not to delete storage upon termination.

@ghost ghost closed this as completed Aug 15, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants