Register the MapsMessaging REST endpoint with Consul

[mbuckton]

What changed

• read the rest endpoint from service metadata
• register its address and port as the MapsMessaging Consul service
• preserve the full messaging endpoint map as Consul service metadata
• run the TCP health check against the advertised REST endpoint
• determine the advertised local address using the OS route to the configured Consul host
• reject missing, malformed, or wildcard REST endpoints
• support IPv4 and IPv6 endpoints

Why

The existing registration advertises a hard-coded port and asks the Consul agent to check localhost. That checks the Consul agent's host rather than the MapsMessaging server when Consul is remote.

Route-based address selection also avoids advertising an unrelated interface on multi-homed systems.

Companion change

MapsMessaging server PR: Maps-Messaging/mapsmessaging_server#2170

Validation

Added focused tests covering IPv4, IPv6, missing endpoints, malformed endpoints, wildcard addresses, route-based local-address selection, and invalid Consul URLs. git diff --check passes.

The Maven test could not run in the available environment because Maven Central is not reachable and no dependency cache is available.

[coderabbitai]

Important

Review skipped

Draft detected.

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 995d3538-c394-451f-b4a5-098f803eb1c2

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

---

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