Skip to content

feat: add allowUnsecureConnection flag to suppress warning (#119)#129

Open
kausiksikdar wants to merge 1 commit intoqdrant:masterfrom
kausiksikdar:fix-unsecure-warning-flag
Open

feat: add allowUnsecureConnection flag to suppress warning (#119)#129
kausiksikdar wants to merge 1 commit intoqdrant:masterfrom
kausiksikdar:fix-unsecure-warning-flag

Conversation

@kausiksikdar
Copy link
Copy Markdown

@kausiksikdar kausiksikdar commented Apr 6, 2026

/claim #119

Summary

Adds an optional configuration flag allowUnsecureConnection to suppress warnings when API keys are used over unsecure connections.

Motivation

In controlled environments (e.g., internal services behind VPN), unsecure connections may be acceptable and warnings can clutter logs.

Changes

  • Added allowUnsecureConnection flag to client configuration
  • Updated warning logic in both gRPC and REST clients
  • Preserved default behavior

Testing

  • Verified warning appears when flag is false
  • Verified warning is suppressed when flag is true

Demo

Tested locally:

Case 1: Default config (allowUnsecureConnection = false)
→ Warning is shown

Case 2: allowUnsecureConnection = true
→ Warning is suppressed

This confirms expected behavior.

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.

1 participant