Validate OTLP gRPC endpoint does not include path

[aryan735]

What

• Enforces validation that OTLP gRPC endpoints must not include a URL path
• Surfaces invalid OTEL_EXPORTER_OTLP_ENDPOINT errors during exporter creation

Why

• gRPC OTLP exporters require host:port only
• Endpoints like /v1/traces are HTTP-specific and invalid for gRPC
• Prevents silent misconfiguration

How

• Ensure loadEnvConfig() is invoked during exporter initialization
• Add tests covering valid and invalid endpoint formats

Tests

• TestEndpointWithPath_ShouldFail
• TestEndpointWithoutPath_ShouldPass
• Test available in pkg : otlptracegrpc
• Test file name : grpc_test.go

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aryan735 / name: Aryan Raj (36c5368, dfd480c)

[dmathieu]

While this validation makes sense, the approach taken is really hard to read and doesn't follow the common Go patterns.
We shouldn't need a global variable for this. And otlptrace.New() already does some validation. This one can happen here.

[aryan735]

While this validation makes sense, the approach taken is really hard to read and doesn't follow the common Go patterns. We shouldn't need a global variable for this. And otlptrace.New() already does some validation. This one can happen here.

Thanks for the review.
I’ve refactored the validation to remove the global error state and moved the OTLP gRPC endpoint path check into New() alongside existing validation.
The fix now returns an error for gRPC endpoints containing a path and passes the updated tests.

Please let me know if any further changes are needed.

[XSAM]

unix://foo/bar (where the bar is the path here) is a valid gRPC endpoint. While I am not sure whether the current implementation supports unix, I am not sure this PR puts unix support in the right direction.

Related:

• open-telemetry/opentelemetry-collector#11941
• open-telemetry/opentelemetry-go-contrib#6636

[XSAM]

I am not sure it is necessary to validate a grpc endpoint by ourselves. Should we just pass it to the gRPC client and let it decide?