Work in progress

[tburghart]

I've got a working implementation of an update that:

• Adds support for deprecated and ignored settings similar to what's described in [Feature request] Support 'deprecated' and/or 'ignore' mapping attributes Kyorai/cuttlefish#39
• Updates the VM schema to current OTP settings.
• Moves closer to a single merged version of the Basho and Kyorai upstream repos.

Posting as an issue here for tracking purposes.

[martinsumner]

Something I've been thinking about is about a pipeline for generating configuration references in the docs (in whatever form the docs may be in the future). It would be good in the docs world, if we just had to know what schema files were used and had markdown generated automatically.

For example, if we make rel in riak, as well as produing a riak.conf could it also produce a series of riak_core.schema.md, riak_kv.schema.md, bitcask.schema.md files etc that can be imported easily into the docs.

[martinsumner]

As well as deprecated maybe an {introduced, Msg :: string()} would then be helpful. So when generating configuration docs we can see what version that option/feature was introduced

[tburghart]

I like the idea of the introduced tag, but that entails work in the doc generator that the deprecated and ignored tags don't - as implemented, they implicitly turn on the hidden flag and cause a warning to be logged when they're encountered in a conf file, so they conveniently avoid any changes to the conf file template generator.

Maybe introduced and some manner of doc generation hook could be a distinct issue, or even two distinct issues? The former would probably not be difficult, the latter would require some serious thinking about how to make the output consumable or at least reference-able with (presumably relative?) path/file#item.key notation.

The implementation for this is essentially complete, it's simply been sidelined at present due to internal priorities. I do hope to get it up onto our branch before very much longer.

[tburghart]

Deprecated/obsolete functionality has finally been pushed to the wday-develop-3.2 branch with documentation in the wiki.