feat: Toggleable use_https param for flags

[matthewestopinal]

Defaults to true. Allows disabling use_https to allow passing through http connections without cert checking or failing the TLS handshake. To be used for dev / local environments.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge with no outstanding code findings.

The concrete configurations preserve their existing positional layouts, default to HTTPS, and consistently apply the selected scheme to both synchronous and asynchronous clients. Both previous threads were manually resolved.

Important Files Changed

Filename	Overview
mixpanel/flags/types.py	Places use_https after existing concrete configuration fields to preserve positional argument compatibility.
mixpanel/flags/local_feature_flags.py	Selects the local feature-flag client URL scheme from use_https.
mixpanel/flags/remote_feature_flags.py	Selects the remote feature-flag client URL scheme from use_https.
mixpanel/flags/test_local_feature_flags.py	Covers transport selection, positional compatibility, URL construction, and proxy headers.
mixpanel/flags/test_remote_feature_flags.py	Covers transport selection, URL construction, and proxy headers.

_{Reviews (4): Last reviewed commit: "fix positional bug" | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.48%. Comparing base (091b056) to head (1e5c5d1).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #198      +/-   ##
==========================================
+ Coverage   96.39%   96.48%   +0.08%     
==========================================
  Files          15       15              
  Lines        2888     2959      +71     
  Branches      176      180       +4     
==========================================
+ Hits         2784     2855      +71     
  Misses         67       67              
  Partials       37       37              

Flag	Coverage Δ
openfeature-provider	51.20% <50.00%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[efahk]

recommend using 'verifyCert' similar to what tracking uses in init.py

[efahk]

Just needs to be on the base FlagsConfig

[tylerjroach]

Is this change coming from as customer request? I'd prefer not to lower the security posture, even if https is still the default.

[matthewestopinal]

Is this change coming from as customer request? I'd prefer not to lower the security posture, even if https is still the default.

@tylerjroach This is coming from internal needs to develop against. Some of our internal devbox servers are sending traffic through http, and if we don't have an option to support it here we have to standup a certain amount of infrastructure just to allow a request to go through in devbox

[tylerjroach]

Got it. Maybe we can sync tomorrow and discuss options here a bit more.