Cookbook should support configuration changes within the dse.yaml file

[cmlicata]

Currently, the cookbook does not support configuration changes to the dse.yaml file, but it does, obviously, support changes to the cassandra.yaml file.

This should be supported in case users would like to support LDAP authentication with Cassandra as well as any other features that you can find here.

[cmlicata]

I would like to take this on, but I am not exactly a chef expert. @michaelklishin, do you have any advice for how to tackle this issue.

Additionally, thanks to Target, I found this cookbook, which I believe can be adapted for our purpose.

[michaelklishin]

What do you mean by "support configuration changes"? Render dse.yaml using Chef attributes? Tell DSE to reload the config? Both? Anything else?

[cmlicata]

Sorry for the lack of specificity. The current cookbook does not render the dse.yaml using Chef Attributes. It simply installs DSE and starts it, whereas, for the cassandra.yaml, your cookbook actually will render it using Chef attributes.

[michaelklishin]

@cmlicata OK. Then it's should be as easy as adding some decent attribute defaults and a template that we render based on them. You already have examples in this cookbook but there's also a fairly small Neo4J Server cookbook that might have more approachable examples. And don't forget the specs :)

Feel free to borrow ideas and code from the Target's DSE cookbook as long as we abide by the Apache 2.0 license they use :)