Skip to content

auto-docs: Update property docs for tag v26.1.10#1745

Merged
JakeSCahill merged 3 commits into
mainfrom
update-property-docs-v26.1.10
Jun 15, 2026
Merged

auto-docs: Update property docs for tag v26.1.10#1745
JakeSCahill merged 3 commits into
mainfrom
update-property-docs-v26.1.10

Conversation

@vbotbuildovich

Copy link
Copy Markdown
Contributor

This PR auto-generates updated Redpanda property documentation for v26.1.10.

@vbotbuildovich vbotbuildovich requested a review from a team as a code owner June 12, 2026 15:54
@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit 6619a25
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-docs-preview/deploys/6a2fbb77baa1ca0008594e03
😎 Deploy Preview https://deploy-preview-1745--redpanda-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8755437f-9a0e-45f8-bf1c-da7556f5894c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR updates Redpanda documentation for the v26.1.10 release. It bumps version metadata in antora.yml, introduces three new configuration properties (Iceberg schema case-insensitivity and OIDC HTTP proxy credentials), updates property metadata in the overrides catalog and schema reference, creates a v26.1.10 property changelog, adds comprehensive AsciiDoc documentation for new and modified properties (including Iceberg and OIDC configurations), and standardizes cross-reference paths across topic, broker, and storage property documentation files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • redpanda-data/docs#1711: Adds features_auto_finalization for v26.1.9; this PR updates its version metadata to v26.1.9.
  • redpanda-data/docs#1611: Updates election_timeout_ms to integer type with default 1500 and adds raft_election_timeout_ms exclude-from-docs marking.
  • redpanda-data/docs#1693: Extends OIDC forward-proxy documentation beyond oidc_http_proxy_url to include username/password credentials.

Suggested reviewers

  • paulohtb6
  • Feediver1
  • micheleRP
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is minimal but adequate. However, it lacks the structured template elements like JIRA ticket reference, page previews, and check categories that are specified in the repository template. Enhance the description by including the JIRA ticket reference, Netlify preview links, review deadline if applicable, and checking the appropriate box from the template categories (e.g., 'Small fix' or 'Content gap').
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating property documentation for Redpanda v26.1.10 release, which aligns with all file modifications across version metadata, configuration properties, and documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch update-property-docs-v26.1.10

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
docs-data/property-overrides.json (1)

843-843: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove literal + markers from enable_consumer_group_metrics description.

The + characters in this JSON string look like patch artifacts and will render as literal text instead of clean paragraph spacing.

Proposed fix
-      "description": "List of enabled consumer group metrics. Accepted values include:\n\n- `group`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_consumers[`redpanda_kafka_consumer_group_consumers`] and xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_topics[`redpanda_kafka_consumer_group_topics`] metrics.\n- `partition`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_committed_offset[`redpanda_kafka_consumer_group_committed_offset`] metric.\n- `consumer_lag`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_lag_max[`redpanda_kafka_consumer_group_lag_max`] and xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_lag_sum[`redpanda_kafka_consumer_group_lag_sum`] metrics\n+\nEnabling `consumer_lag` may add a small amount of additional processing overhead to the brokers, especially in environments with a high number of consumer groups or partitions.\n+",
+      "description": "List of enabled consumer group metrics. Accepted values include:\n\n- `group`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_consumers[`redpanda_kafka_consumer_group_consumers`] and xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_topics[`redpanda_kafka_consumer_group_topics`] metrics.\n- `partition`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_committed_offset[`redpanda_kafka_consumer_group_committed_offset`] metric.\n- `consumer_lag`: Enables the xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_lag_max[`redpanda_kafka_consumer_group_lag_max`] and xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_lag_sum[`redpanda_kafka_consumer_group_lag_sum`] metrics.\n\nEnabling `consumer_lag` may add a small amount of additional processing overhead to the brokers, especially in environments with a high number of consumer groups or partitions.",

As per coding guidelines, property descriptions should use \n\n for paragraph breaks rather than inline patch markers.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs-data/property-overrides.json` at line 843, The description string for
the property enable_consumer_group_metrics contains stray '+' characters (patch
artifacts) that will render literally; remove those '+' markers and replace them
with proper paragraph breaks (use "\n\n") so the sentence about additional
processing overhead is a separate paragraph, and ensure the final JSON string
has no leading/trailing '+' characters and preserves existing newline escapes.

Source: Coding guidelines

modules/reference/partials/properties/cluster-properties.adoc (1)

5417-5455: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify the timeout rename/alias.

election_timeout_ms and raft_election_timeout_ms describe the same setting, but the page never says which name is canonical. Please add an alias/forward-reference or remove one entry so readers and downstream tooling don't end up with two authoritative keys for one config.

Also applies to: 15148-15195

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@modules/reference/partials/properties/cluster-properties.adoc` around lines
5417 - 5455, This page defines the same property under two names; update the
text to state a single canonical name and mark the other as an alias: choose
"election_timeout_ms" as the canonical property and add a short clarifying
sentence in the election_timeout_ms block like "Alias: raft_election_timeout_ms"
(or vice‑versa if you prefer the other as canonical), and remove the duplicate
full entry for the aliased name so downstream tools/readers only have one
authoritative key; ensure both occurrences (the current block for
election_timeout_ms and the other block referencing raft_election_timeout_ms)
include the alias wording and identical metadata.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@modules/reference/partials/properties/broker-properties.adoc`:
- Line 2496: The xref targets were normalized incorrectly—update the Antora xref
IDs to include the properties/ segment and full module-prefixed resource IDs:
change any occurrences of reference:cluster-properties.adoc to
reference:properties/cluster-properties.adoc in
modules/reference/partials/properties/broker-properties.adoc (the rack link) and
the corresponding cluster property xrefs in
modules/reference/partials/properties/topic-properties.adoc; ensure each xref
uses the full Antora resource ID with module prefix so links resolve
consistently.

In `@modules/reference/partials/properties/cluster-properties.adoc`:
- Around line 9019-9065: Add the release-provenance marker to the new property
section for iceberg_schema_case_insensitive by inserting the line "*Introduced
in v26.1.10*" under the property title/description (match the style used
elsewhere in the file), and apply the same marker to any other newly added
property sections in this file so all new entries include the release note;
locate sections by the property name iceberg_schema_case_insensitive and any
other recently added property headers to mirror the exact formatting and
placement.

---

Outside diff comments:
In `@docs-data/property-overrides.json`:
- Line 843: The description string for the property
enable_consumer_group_metrics contains stray '+' characters (patch artifacts)
that will render literally; remove those '+' markers and replace them with
proper paragraph breaks (use "\n\n") so the sentence about additional processing
overhead is a separate paragraph, and ensure the final JSON string has no
leading/trailing '+' characters and preserves existing newline escapes.

In `@modules/reference/partials/properties/cluster-properties.adoc`:
- Around line 5417-5455: This page defines the same property under two names;
update the text to state a single canonical name and mark the other as an alias:
choose "election_timeout_ms" as the canonical property and add a short
clarifying sentence in the election_timeout_ms block like "Alias:
raft_election_timeout_ms" (or vice‑versa if you prefer the other as canonical),
and remove the duplicate full entry for the aliased name so downstream
tools/readers only have one authoritative key; ensure both occurrences (the
current block for election_timeout_ms and the other block referencing
raft_election_timeout_ms) include the alias wording and identical metadata.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: eff90727-62bd-4c18-80aa-c7c1e9735180

📥 Commits

Reviewing files that changed from the base of the PR and between d47c541 and c6e3e8b.

📒 Files selected for processing (9)
  • antora.yml
  • docs-data/property-overrides.json
  • docs-data/redpanda-property-changes-v26.1.8-to-v26.1.9.json
  • docs-data/redpanda-property-changes-v26.1.9-to-v26.1.10.json
  • modules/reference/attachments/redpanda-properties-v26.1.10.json
  • modules/reference/partials/properties/broker-properties.adoc
  • modules/reference/partials/properties/cluster-properties.adoc
  • modules/reference/partials/properties/object-storage-properties.adoc
  • modules/reference/partials/properties/topic-properties.adoc
💤 Files with no reviewable changes (1)
  • docs-data/redpanda-property-changes-v26.1.8-to-v26.1.9.json

Comment thread modules/reference/partials/properties/broker-properties.adoc
Comment thread modules/reference/partials/properties/cluster-properties.adoc
@kbatuigas

Copy link
Copy Markdown
Contributor

@JakeSCahill I ran source verification and re-ran the generation tool locally to confirm these findings.

```bash
GITHUB_TOKEN=$(gh auth token) node_modules/.bin/doc-tools generate property-docs
--tag v26.1.10
--diff v26.1.9
--generate-partials
```

Critical issues (tool bugs — need a fix before merge or a follow-up)

1. Broken xrefs in topic-properties.adoc (29 instances)

The "Corresponding cluster property" table rows in topic-properties.adoc were changed from:
```
xref:reference:properties/cluster-properties.adoc#...
```
to:
```
xref:reference:cluster-properties.adoc#...
```
The properties/ path segment is required because the pages live at modules/reference/pages/properties/cluster-properties.adoc. Without it, these xrefs won't resolve in Antora. I re-ran the generator and it produces the same broken output, so this is a template bug in docs-extensions-and-macros.

2. Wrong xref target for three cloud_storage_enable_remote_* properties

The same xref change also affects redpanda.remote.allowgaps, redpanda.remote.read, and redpanda.remote.write — but these are doubly wrong because their sections are in object-storage-properties.adoc, not cluster-properties.adoc. Same root cause (template bug).

Suggestion

3. Missing "Introduced in v26.1.10" markers

iceberg_schema_case_insensitive, oidc_http_proxy_password, and oidc_http_proxy_username all have "version": "v26.1.10" in property-overrides.json but the generated AsciiDoc doesn't include the *Introduced in v26.1.10* marker. Other new properties in this file (e.g. features_auto_finalization) have the marker correctly. Also a template issue.

What works well

  • election_timeout_ms type/default corrected to integer/1500
  • topic_memory_per_partition default resolved from constant name to 200 KiB (204800)
  • delete_topic_enable description and related topics improved ✅
  • BYOC tags added correctly for iceberg_dlq_table_suffix and iceberg_rest_catalog_gcp_user_project
  • iceberg_rest_catalog_request_auth_mode adds gcp enum and fixes typo ✅
  • xref fixes in broker-properties.adoc and object-storage-properties.adoc are correct ✅

JakeSCahill and others added 2 commits June 15, 2026 08:52
Re-ran doc-tools to add "Introduced in v26.1.10" markers for:
- iceberg_schema_case_insensitive
- oidc_http_proxy_password
- oidc_http_proxy_username

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- iceberg_schema_case_insensitive: Use "for example" instead of "e.g.",
  use backticks for `auto` value
- oidc_http_proxy_url: Remove em dash, use backticks for URLs and
  property references
- oidc_http_proxy_password: Use backticks for `oidc_http_proxy_url` ref
- oidc_http_proxy_username: Use backticks for `oidc_http_proxy_url` ref

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@JakeSCahill JakeSCahill merged commit fe589e2 into main Jun 15, 2026
6 of 7 checks passed
@JakeSCahill JakeSCahill deleted the update-property-docs-v26.1.10 branch June 15, 2026 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants