[main](forwardport #45815) [9.0](backport #45772) [docs automation] Update generate_fields_docs.py to add applies_to badges

[mergify]

Note

Starting with v9.0, there is no longer a new documentation set published with every minor release: the same page stays valid over time and shows version-related evolutions. Read more in Write cumulative documentation.

Related to #45436, https://github.com/elastic/docs-content-internal/issues/128

Updates generate_fields_docs.py to add more applies_to badges as needed. Currently we're only adding deprecated badges to fields when there's a deprecated property in fields.yml. In addition to those, we want to add an applies_to badge when:

• There's a release specified (usually included if beta or preview).
• There's a new version property specified as described in [docs] [proof-of concept] Make it possible to add applies_to labels to generated docs #45436. This allows contributors to include version information over time for fields or groups of fields. For example, for a field that was added in beta in 9.0.0 and then went GA in 9.1.0, you would add:

  version:
    beta: 9.0.0
    ga: 9.1.0

To test out the new version property, I added a version to fields.yml files that contained new fields in 9.1.0 from these two PRs:

• [Metricbeat] Add JetStream metricset to NATS module #43310
• [metricbeat] [meraki] add VPN metrics #44851

I also made some slight formatting changes to improve how definition lists are rendered (indenting all lines in a definition list item).

Some notes for the reviewers:

• I don't have a lot of experience writing in Python so please let me know if anything can be improved.
• I'm not sure if there are contributing guidelines that should be updated to reflect these changes.

  ---

  This is an automatic backport of pull request [docs automation] Update generate_fields_docs.py to add applies_to badges #45772 done by Mergify.

  ---

  This is an automatic backport of pull request [9.0](backport #45772) [docs automation] Update generate_fields_docs.py to add applies_to badges #45815 done by Mergify.

[mergify]

Cherry-pick of 1121991 has failed:

On branch mergify/bp/main/pr-45815
Your branch is up to date with 'origin/main'.

You are currently cherry-picking commit 112199148.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/reference/filebeat/exported-fields-winlog.md
	both modified:   docs/reference/metricbeat/exported-fields-kubernetes.md
	both modified:   docs/reference/metricbeat/exported-fields-nats.md
	both modified:   docs/reference/metricbeat/exported-fields-system.md

no changes added to commit (use "git add" and/or "git commit -a")

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

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[github-actions]

🔍 Preview links for changed docs

• docs/reference/filebeat/exported-fields-winlog.md
• docs/reference/metricbeat/exported-fields-kubernetes.md
• docs/reference/metricbeat/exported-fields-nats.md
• docs/reference/metricbeat/exported-fields-system.md

[colleenmcginnis]

I'm not sure why this, a forwardport of a backport, was opened by mergify. These changes were already merged into main in #45772. I'm going to close, but reopen if I'm missing something...