Dan Torrey

Note: These configuration settings are not used in the new index creation flow, and are only used in some older migrations. The defaults for the new index flow are currently...

> I was just looking at this. Do these LUT entities need this even though they'll be installed outside the Illuminate content-pack pipeline, in the new code for @kingzacko1 changes?...

Thanks @boosty. I'll finish this up with current defaults, and we can continue accepting more feedback while the review is in progress.

It turns out that the `elasticsearch_shards` and `elasticsearch_replicas` server settings are not actually used in the standard new index creation flow, and are only used in some older migrations. The...

Looping in @dennisoelkers for early feedback in case you see anything noteworthy so far.

> Can you please check the existing index-set-related migrations if there is anything we need to adjust for this? Thank you! @bernd Thanks for mentioning those. I saw them, but...

> Just wanted to mention that once merged, we should decide if we are also changing the defaults as discussed here: [Graylog2/graylog-plugin-enterprise#3264](https://github.com/Graylog2/graylog-plugin-enterprise/issues/3264) > > Could make sense to announce and...

I am still making progress on this. I now have it working end-to-end. The Configurations page has an Index Defaults section, and the defaults are now used on the Create...

The frontend is now working end-to-end for all property types (including those that are pluggable [retention and rotation strategies]). Now, I need to implement fall-back defaults support for the configuration...

@boosty @rich-graylog @waab76 An update on this feature with respect to Graylog `5.0`: Development of the core functionality (frontend/backend) is now done, which provides the ability to specify database-defaults at...