Stop supporting deprecated syntax for config source expansion #5832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The expansion of bare config sources is no longer supported.
Strings like
$ENV
or$include:/path/to/file.yaml
will no longer be expanded. Instead, use the${env:ENV}
or${include:/path/to/file.yaml}
syntax. Only two symbols are allowed after$
:{
and$
. The collector will log an error and fail to start if it encounters a bare config source expansion.This syntax has been deprecated since version 0.105.0.
The reason for this change is aligning with OpenTelemetry Collector upstream, where this syntax has been removed in 0.104.0 version. Long term plan is to do not have the custom config sources in this repository, instead consolidate the functionality with the upstream confmap providers.