Fog doesn't respect "delete_on_termination" option in elasticsearch::ebs

[abstrctn]

When using the elasticsearch::ebs recipe, you can specify options to configure the EBS Volume that will be created and attached to your instance:

"devices" : {
  "/dev/sda2" : {
    "ebs" : {
      "delete_on_termination" : true,
    }
  }
}

These options are largely passed through to the Fog gem, which initializes and saves a new Volume object with those parameters. However, as has been documented in the Fog gem, the delete_on_termination option is ignored when initializing a new EBS Volume: fog/fog#1737

Until there is a fix on the gem side, it looks like the delete_on_termination flag may need to be set in the recipe by modifying the appropriate AWS instance attribute.

[karmi]

Hi, thanks, I think all of us just ignored that and I agree it's painful especially when you fire up nodes for testing etc. I'll have a look how we can fix this directly in the Fog gem -- thanks for the issue link!

[dmorrison]

Just ran into this myself. Any updates? Thanks!

[karmi]

@dmorrison No, sorry, started looking into it at that time, and it was much more complicated then I originally thought...

[martinb3]

Hello! We've re-written the cookbook using libraries that expose resources and providers, and we've removed support for the EBS recipe. I would recommend using the AWS chef cookbook for this use case now. We figured it would be better to focus on making Elasticsearch's chef experience best, and leave EBS functionality to the folks who know that the best. Hope this helps!