Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,9 @@ release.
`PluginComponentProvider`, `CreatePlugin` to `CreateComponent` in effort to
use consistent vocabulary
([#4806](https://github.com/open-telemetry/opentelemetry-specification/pull/4806))
- Declarative configuration: allow language-specific prefixes in environment
variable substitution.
([#4891](https://github.com/open-telemetry/opentelemetry-specification/pull/4891))

### Supplementary Guidelines

Expand Down
9 changes: 9 additions & 0 deletions specification/configuration/data-model.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,15 @@ DIGIT = %x30-39 ; 0-9
whitespace except `}`
* Must follow with `}`

Language implementations MAY support additional prefixes beyond `env:` to access
Comment thread
jack-berg marked this conversation as resolved.
language-specific configuration sources (e.g., Java system properties). Such
prefixes MUST follow the same syntactic structure as `env:` (prefix followed by
colon). For example, Java implementations may support `sys:` to access system
properties: `${sys:otel.service.name}`. Language-specific prefixes enable
idiomatic configuration patterns while maintaining the universal `env:` prefix
for cross-language compatibility. Language implementations SHOULD document any
additional prefixes they support.

`INVALID-SUBSTITUTION-REF` defines an invalid environment variable substitution
reference:

Expand Down
Loading