I would like to write a script that generates a plugin-list.asciidoc file. It would loop through everything in src/plugins and x-pack/plugins and build a link to the readme, or if no readme exists, print a warning in the asciidoc.
If the README was in md, it'd be a link to the Markdown in the repo. If the README is in asciidoc, it'd use the header for the link and add an include line.
I'd also like to hook this into ci so if the output of the command doesn't match the contents inside the generated file, an error would be thrown.
The goals are:
- A central place to link to all of our available plugins and services.
- A guarantee that this list stays up to date.
- A way to easily see which plugins/services are missing READMEs. Adds motivation to add READMEs. Eventually we could even block ci on READMEs existing.
Something like this being autogenerated and guaranteed to be up to date:

I would like to write a script that generates a
plugin-list.asciidocfile. It would loop through everything insrc/pluginsandx-pack/pluginsand build a link to the readme, or if no readme exists, print a warning in the asciidoc.If the README was in md, it'd be a link to the Markdown in the repo. If the README is in asciidoc, it'd use the header for the link and add an
includeline.I'd also like to hook this into ci so if the output of the command doesn't match the contents inside the generated file, an error would be thrown.
The goals are:
Something like this being autogenerated and guaranteed to be up to date: