-
Notifications
You must be signed in to change notification settings - Fork 5k
[9.0](backport #44793) [documentation][exported-fields] update autogeneration scripts to generate markdown #44803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Cherry-pick of 00dcc0c has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
This pull request has not been merged yet. Could you please review and merge it @VihasMakwana? 🙏 |
Proposed commit message
This is a follow-up of #44638.
This PR takes care of autogeneration of
exported-fields.mddocument for each beat.Unfortunately, it is not possible to break down this into PR for each beat because this particular autogeneration script is shared by each beat and is under
libbeat. Updatingdev-tools/mage/docs.goandlibbeat/scripts/generate_fields_docs.pywill update generateexported-fieldsfor each beat.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR
Exported Fieldssection for each beat.Related issues
This is an automatic backport of pull request #44793 done by [Mergify](https://mergify.com).