Fix stale proxy configuration guidance

[BenCodez]

Summary

• update the backend Control credential comments to reflect automatic enrollment over Plugin Messaging, HTTP, Redis, MQTT, MySQL, and sockets
• note the shared secretkey.key requirement for Redis, MQTT, MySQL, and sockets
• replace the obsolete /votingpluginbungee status guidance with /votingpluginproxy status

Scope

Comment-only corrections in the generated default Config.yml and BungeeSettings.yml; runtime behavior is unchanged.

Validation

• both changed files parse as valid YAML
• git diff --check
• independent pre-PR review: no findings
• local Maven tests were not run because this runner lacks Maven and Java 21; repository CI is expected to provide the authoritative build

AI disclosure: This content was written with assistance from ChatGPT.

Summary by CodeRabbit

• Bug Fixes

  • Updated the HTTP communication-status command to use /votingpluginproxy status.

• Documentation

  • Clarified how backend credentials are generated and which connection methods require matching key files on the proxy and backend.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 532d7a74-4fee-4cc0-aa82-a3250a9e21ab

📥 Commits

Reviewing files that changed from the base of the PR and between 07454ac and e24321d.

📒 Files selected for processing (2)

• VotingPlugin/src/main/resources/BungeeSettings.yml
• VotingPlugin/src/main/resources/Config.yml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (1)

Source excerpt: `auto-create-vote-sites` is intentionally narrower than `common-settings`: it reads/writes only `Config.yml -> AutoCreateVoteSites`.

📄 CodeRabbit inference engine (AGENTS.md)

Files:

• VotingPlugin/src/main/resources/Config.yml

🔇 Additional comments (2)

VotingPlugin/src/main/resources/BungeeSettings.yml (1)

104-104: 🎯 Functional Correctness

The comment is correct. votingpluginproxy is registered, and status sends communication status messages. No update is needed.

VotingPlugin/src/main/resources/Config.yml (1)

1204-1205: 🗄️ Data Integrity & Integration

The transport matrix is supported. The proxy skips the enrollment listener for Plugin Messaging and HTTP. For every other method, it verifies requests and signs results with secretkey.key. The backend uses the same split and loads secretkey.key for all other methods, including Redis, MQTT, sockets, and MySQL. The review comment is refuted.

---

📝 Walkthrough

Walkthrough

Two configuration comments were updated. One names the HTTP status command. The other describes credential-enrollment paths and secret-key requirements.

Changes

HTTP status command

Layer / File(s)	Summary
Update status command reference VotingPlugin/src/main/resources/BungeeSettings.yml	The comment now uses /votingpluginproxy status for the HTTP communication-status command.

Credential enrollment

Layer / File(s)	Summary
Update enrollment instructions VotingPlugin/src/main/resources/Config.yml	The comment now describes enrollment through locally hosted Control or authenticated proxy transport. It also specifies matching secretkey.key files for Redis, MQTT, sockets, and MySQL.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to e2432

The updated setup guidance matches the verified command and enrollment paths. No issue identified prevents merging.

Architecture Summary

Architecture risk: 🔵 Low · up to e2432

The change affects 1 system.

Changed systems: VotingPlugin

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — VotingPlugin (service) was modified; 2 changed files map to changed impact.

Before / after behavior

• observed — Modified behavior in VotingPlugin/src/main/resources/BungeeSettings.yml: The HTTP communication-status command in the comment changed from /votingpluginbungee status to /votingpluginproxy status.
• observed — Modified behavior in VotingPlugin/src/main/resources/Config.yml: The credential-enrollment documentation now includes the configured authenticated proxy transport alongside locally hosted Control, and specifies that Redis, MQTT, sockets, and MySQL enrollment also requires matching secretkey.key files on proxy and backend; the prior comment referred only to the proxy’s authenticated, route-verified plugin-message path.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating stale proxy configuration guidance in the YAML files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-29T01:22:28.857073Z	e24321d	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-29T01:22:47.673240Z	e24321d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.