Revert changes introduced in open-telemetry#3730

pellared · Oct 30, 2023 · 6529f40 · 6529f40
1 parent 2fbb504
commit 6529f40
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -25,9 +25,6 @@ release.
 - New exporter implementations do not need to support
   `OTEL_EXPORTER_OTLP_SPAN_INSECURE` and `OTEL_EXPORTER_OTLP_METRIC_INSECURE`.
   ([#3719](https://github.com/open-telemetry/opentelemetry-specification/pull/3719))
-- Clarify that the configuration options MAY be implemented by the exporter,
-  the SDK, or a separate component (e.g. environment-based autoconfiguration component).
-  ([#3719](https://github.com/open-telemetry/opentelemetry-specification/pull/3719))
 
 ### Compatibility
 

diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md
@@ -11,7 +11,6 @@ This document specifies the configuration options available to the OpenTelemetry
 ## Configuration Options
 
 The following configuration options MUST be available to configure the OTLP exporter.
-The configuration options MAY be implemented directly in the OTLP exporter, in the SDK, or in a separate component (e.g. environment-based autoconfiguration component).
 Each configuration option MUST be overridable by a signal specific option.
 
 - **Endpoint (OTLP/HTTP)**: Target URL to which the exporter is going to send spans or metrics. The endpoint MUST be a valid URL with scheme (http or https) and host, MAY contain a port, SHOULD contain a path and MUST NOT contain other parts (such as query string or fragment). A scheme of https indicates a secure connection. When using `OTEL_EXPORTER_OTLP_ENDPOINT`, exporters MUST construct per-signal URLs as  [described below](#endpoint-urls-for-otlphttp). The per-signal endpoint configuration options take precedence and can be used to override this behavior (the URL is used as-is for them, without any modifications). See the [OTLP Specification][otlphttp-req] for more details.