node_id_overrides can be removed after use

[vuldin]

Description

Resolves https://redpandadata.atlassian.net/browse/
Review deadline:

Page previews

https://deploy-preview-1356--redpanda-docs-preview.netlify.app/current/reference/properties/broker-properties/#node_id_overrides

Checks

• New feature
• Content gap
• Support Follow-up
• Small fix (typos, links, copyedits, etc)

[coderabbitai]

📝 Walkthrough

Walkthrough

The broker-properties.adoc page updates the description of node_id_overrides to specify fields: current_uuid, new_id, new_uuid, and ignore_existing_node_id. The applicability condition now requires current_uuid to match the broker’s actual UUID. A note instructs removal of the property after a successful cluster restart to avoid reapplication and ensure consistent configuration across brokers. Additionally, a trailing newline was added to the Audit Log Client note (formatting only).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• c4milo
• kbatuigas

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description follows the repository template structure and includes a page preview and the checked "Support Follow-up" box, but required fields are incomplete: the Jira reference remains the placeholder "" and the "Review deadline" is blank, leaving essential tracking information missing. Because those template fields are expected to be filled, the description is incomplete and should be updated before merging.	Replace the "" placeholder with the actual Jira ticket URL or ID, add a concrete review deadline date, and confirm that the provided page preview(s) cover all modified files; after those fields are completed the description will meet the template requirements.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "node_id_overrides can be removed after use" succinctly and accurately summarizes the main documentation change—the added guidance to remove the node_id_overrides setting after a successful restart to avoid reapplication. It is specific, focused, and suitable as a single-line PR summary that a teammate scanning history will understand.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch vuldin-patch-2

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 356bdb7 and 3400714.

📒 Files selected for processing (1)

• modules/reference/pages/properties/broker-properties.adoc (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Redirect rules - redpanda-docs-preview
• GitHub Check: Header rules - redpanda-docs-preview
• GitHub Check: Pages changed - redpanda-docs-preview

🔇 Additional comments (1)

modules/reference/pages/properties/broker-properties.adoc (1)

1351-1351: LGTM: formatting-only newline.

No content change; good to keep a trailing newline.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[netlify]

✅ Deploy Preview for redpanda-docs-preview ready!

Name	Link
🔨 Latest commit	3400714
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-docs-preview/deploys/68c871fd9d5bf00008fe0c9f
😎 Deploy Preview	https://deploy-preview-1356--redpanda-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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