Can't run default, server and api_access cookbooks in one pass about graylog2-cookbook HOT 4 CLOSED

Thanks for the report!
This is exactly the reason why the api_access recipe is not in the kitchen.yml. For the 2.0 version of this cookbook we deleted the recipe completly in favor of content pack auto loading. With newer versions of Graylog you can place a json file somewhere and let Graylog-server load it at start-up time. With this you can create Inputs, Streams, Dashboards... Take a look here: https://github.com/Graylog2/graylog2-server/blob/master/misc/graylog.conf#L393

from graylog2-cookbook.

Thanks, I will take a look at that. Is the 2.0 branch in a state where you would say it's safe to start consuming (with some disclaimers around ongoing development obvious ;) )?

from graylog2-cookbook.

We just updated our own instance to GL 2.0 with it, so it's pretty ok already. But it's possible that there will be changes in the near future in that branch.

from graylog2-cookbook.

Thanks for the feedback. I was able to get this working with the new attribute overrides and managing our own JSON file with the inputs setup.

One thing that could be handy would:

• Update LWRPs that leveraged the api_access cookbook such as inputs to instead write out shell content_pack templates to the auto-load folder
• dynamic management of the base default['graylog2']['server']['content_packs_auto_load'] attribute to aggregate all of the LWRP's templates

That way, as a user I would simply need to declare what I wanted (inputs, dahsboard, etc.) through Chef and not need to worry about managing the various attributes & JSON templates.

from graylog2-cookbook.