Autodetect & Handle TLS for Lumera gRPC Connections

[mateeullahmalik]

Autodetect & Handle TLS for Lumera gRPC Connections

Why

Operators enter Lumera endpoints in mixed formats (https://…, grpcs://…, host:443, plain host:9090).
The original dialer hard-coded h2c (insecure.NewCredentials()), so any URL that expected TLS failed. We want:

• Zero-config: accept whatever string the user pastes in.

• Back-compat: plaintext still works for local/test nets.

• No extra flags: behaviour inferred from the address itself.

---

What’s inside

• lumera/connection.go fully replaced

  • Parses address with normaliseAddr():

    • https:// or grpcs:// ⇒ TLS, default port 443

    • Any :443 ⇒ TLS

    • Everything else ⇒ insecure h2c

  • Selects credentials.NewClientTLSFromCert(nil, serverName) for TLS, otherwise insecure.NewCredentials().

  • Keeps public Connection interface unchanged.

• No external deps added – still uses Go stdlib + google.golang.org/grpc.

---

[Copilot]

Pull Request Overview

This PR introduces automatic TLS detection for Lumera gRPC connections based on the provided address format, replacing the previous hard-coded insecure connection approach. The implementation accepts various address formats (https://, grpcs://, host:443, plain host) and automatically selects appropriate transport credentials without requiring additional configuration flags.

Key changes:

• Automatic TLS detection based on address scheme or port 443
• Support for multiple address formats while maintaining backward compatibility
• Removal of hard-coded insecure credentials in favor of dynamic selection

Comments suppressed due to low confidence (1)

pkg/lumera/connection.go:100

• The variable name 'splitErr' is inconsistent with Go naming conventions. It should be 'err' since it's a standard error variable in this scope.

	if splitErr != nil {