otlploghttp: support OTEL_EXPORTER_OTLP_LOGS_INSECURE and OTEL_EXPORTER_OTLP_INSECURE env vars

[fd]

This PR applies the same changes as #5739 but for the otlploghttp package.

Like this both otlploggrpc and otlploghttp work the same way.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pellared / name: Robert Pająk (233afe5, 4e59b85)

[dmathieu]

This will need a changelog entry.

[codecov]

Codecov Report

❌ Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.1%. Comparing base (4200d1e) to head (233afe5).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
exporters/otlp/otlplog/otlploghttp/config.go	91.6%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #7608     +/-   ##
=======================================
- Coverage   86.1%   86.1%   -0.1%     
=======================================
  Files        298     298             
  Lines      21675   21694     +19     
=======================================
+ Hits       18676   18692     +16     
- Misses      2624    2626      +2     
- Partials     375     376      +1     

Files with missing lines	Coverage Δ
exporters/otlp/otlplog/otlploghttp/config.go	94.0% <91.6%> (-0.4%)	⬇️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[pellared]

This change is not compliant with OTel Specification: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md. The OTEL_EXPORTER_OTLP_INSECURE is documented only for OTLP/gRPC exporter. Note that otlpmetrichttp and otlptracehttp also do not support such env vars.

You would first have to propose adding such configuration to the OTel Specification.

[fd]

🤔 Then I believe the rust impl is not following the spec. I'll have a look there first.

Thx!

---

Note that otlpmetrichttp and otlptracehttp also do not support such env vars.

This doesn't seem to be the case

opentelemetry-go/exporters/otlp/otlpmetric/otlpmetrichttp/internal/oconf/envconfig.go

Lines 92 to 93 in dafdbf8

	envconfig.WithBool("INSECURE", func(b bool) { opts = append(opts, withInsecure(b)) }),
	envconfig.WithBool("METRICS_INSECURE", func(b bool) { opts = append(opts, withInsecure(b)) }),

opentelemetry-go/exporters/otlp/otlptrace/otlptracehttp/internal/otlpconfig/envconfig.go

Lines 91 to 92 in dafdbf8

	envconfig.WithBool("INSECURE", func(b bool) { opts = append(opts, withInsecure(b)) }),
	envconfig.WithBool("TRACES_INSECURE", func(b bool) { opts = append(opts, withInsecure(b)) }),

So at least the Go impl is also not in compliance with the spec and is internally inconsistent.

[pellared]

I created #7614 as it is better to use an GitHub issue for discussions and tracking.

[pellared]

Approving per #7614 (comment)

[pellared]

@fd, thanks for your contribution. You can also consider updating the doc.go in otlptracehttp, otlpmetrichttp, and otlploghttp in a seperate PR (as support for these env vars are not documented).