Perhaps this is well known to those familiar with chef, ruby, and the plethora of tools used in the Graylog pipeline, but every time I do a `reconfigure` - usually an upgrade - as expected, my graylog.conf and elasticsearch.yml get pushed back into the form chef wants it to be in. Probably the single most dangerous thing here is that the index retention policy gets trampled back to keeping only 40 indices and deleting the oldest. We use Elasticsearch snapshots to snapshot indices on alternative storage before deleting them. Running `reconfigure` can quickly trigger the retention to delete the vast majority of our data. My plugins source their config from graylog.conf. In short, I have need to override the chef values for arbitrary options and I'd like these overrides to remain when I upgrade the debian packages for Graylog.
Any pointers out there? Thanks! -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/76b35f91-cddf-4b60-b2e1-2da5f0c46316%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
