HDDS-14696. [Auto] Update configuration documentation

[asf-ci-deploy]

What changes were proposed in this pull request?

This is an automated pull request triggered by the update-ozone-site-config-doc workflow run from 341b6313962e6a967a89430cd403c2fe66ec1be7 on master.

The configuration documentation has been automatically regenerated from the latest ozone-default.xml files.

What is the link to the Apache JIRA?

HDDS-14696

How was this patch tested?

This is an auto-generated documentation update. Reviewers should verify:

• The markdown file is properly formatted
• Configuration keys are correctly extracted
• No unexpected changes in existing configurations

[errose28]

We're so close! The new page isn't building for some reason.

Also in a follow-up we should update this page to be 99-appendix.md so it is always at the end of the section. I think there's a prefix CI check we'll need to tweak to allow this.

[adoroszlai]

The new page isn't building for some reason.

It seems to have problem with {...} type text, treating them as reference. We have to update Ozone configs and/or xml_to_md.py, wrapping in backticks.

Also in a follow-up we should update this page to be 99-appendix.md so it is always at the end of the section. I think there's a prefix CI check we'll need to tweak to allow this.

Also: disable CI for push event on the automated-config-doc-update branch (only keep pull_request), no need to run CI twice.

[sarvekshayr]

The new page isn't building for some reason.

It seems to have problem with {...} type text, treating them as reference. We have to update Ozone configs and/or xml_to_md.py, wrapping in backticks.

Also in a follow-up we should update this page to be 99-appendix.md so it is always at the end of the section. I think there's a prefix CI check we'll need to tweak to allow this.

Also: disable CI for push event on the automated-config-doc-update branch (only keep pull_request), no need to run CI twice.

I'll create two JIRAs:

1. ozone -> To fix the {...} issue in xml_to_md.py and rename appendix.md.
2. ozone-site -> disable CI for push event on the automated-config-doc-update branch, rename appendix.md and tweak prefix CI check.

[asf-ci-deploy]

What changes were proposed in this pull request?

This is an automated pull request triggered by the update-ozone-site-config-doc workflow run from 8044a55c8ab33bab53a18845991f2dd6a84e2452 on master.

The configuration documentation has been automatically regenerated from the latest ozone-default.xml files.

What is the link to the Apache JIRA?

HDDS-14746

How was this patch tested?

This is an auto-generated documentation update. Reviewers should verify:

• The markdown file is properly formatted
• Configuration keys are correctly extracted
• No unexpected changes in existing configurations

[asf-ci-deploy]

What changes were proposed in this pull request?

This is an automated pull request triggered by the update-ozone-site-config-doc workflow run from 264c44679de0a5a3f83668af33895ed45cf6fe0b on master.

The configuration documentation has been automatically regenerated from the latest ozone-default.xml files.

What is the link to the Apache JIRA?

HDDS-14744

How was this patch tested?

This is an auto-generated documentation update. Reviewers should verify:

• The markdown file is properly formatted
• Configuration keys are correctly extracted
• No unexpected changes in existing configurations

[adoroszlai]

Filed HDDS-14747 to avoid unnecessary updates to the existing PR when config is not changed by ozone commit.

[asf-ci-deploy]

What changes were proposed in this pull request?

This is an automated pull request triggered by the update-ozone-site-config-doc workflow run from d989dc1c66a0410fff2a84ebe8e0e863741b9ca1 on master.

The configuration documentation has been automatically regenerated from the latest ozone-default.xml files.

What is the link to the Apache JIRA?

HDDS-14745

How was this patch tested?

This is an auto-generated documentation update. Reviewers should verify:

• The markdown file is properly formatted
• Configuration keys are correctly extracted
• No unexpected changes in existing configurations

[asf-ci-deploy]

What changes were proposed in this pull request?

This is an automated pull request triggered by the update-ozone-site-config-doc workflow run from 4d9a7573edb06021403e74ef610331d63ddf6778 on master.

The configuration documentation has been automatically regenerated from the latest ozone-default.xml files.

What is the link to the Apache JIRA?

HDDS-14673

How was this patch tested?

This is an auto-generated documentation update. Reviewers should verify:

• The markdown file is properly formatted
• Configuration keys are correctly extracted
• No unexpected changes in existing configurations