Remove OtlpConfigurationExtensions.OtlpEndpointEnvironmentVariableName

[eerhardt]

Replace usages with KnownOtelConfigNames.ExporterOtlpEndpoint directly.

This change was only needed in main since it never made it to release/13.2.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15390

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 15390"

[Copilot]

Pull request overview

Removes the OtlpConfigurationExtensions.OtlpEndpointEnvironmentVariableName public field and updates internal OTLP env-var wiring to use KnownOtelConfigNames.ExporterOtlpEndpoint directly.

Changes:

• Deleted OtlpConfigurationExtensions.OtlpEndpointEnvironmentVariableName.
• Updated OTLP endpoint environment variable setting/lookup to use KnownOtelConfigNames.ExporterOtlpEndpoint.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/Aspire.Hosting/OtlpConfigurationExtensions.cs	Removes the public env-var name field and writes OTEL_EXPORTER_OTLP_ENDPOINT using KnownOtelConfigNames.
src/Aspire.Hosting/Dcp/OtlpEndpointReferenceGatherer.cs	Reads/writes the OTLP endpoint env var using KnownOtelConfigNames instead of the removed field.

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Hosting-1 / Hosting-1 (windows-latest) - Job-level runner or infrastructure failure matched the transient allowlist.

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Hosting-1 / Hosting-1 (windows-latest) - Job-level runner or infrastructure failure matched the transient allowlist.