[chore] Set missing enabled field for resource_attributes#43085
Merged
dmitryax merged 1 commit intoSep 30, 2025
Conversation
If enabled is unset in metadata.yaml it's defaulted to false. This commit doesn't change any behavior, it only unblocks the stricter validation open-telemetry/opentelemetry-collector#13921 by setting the false value explicitly Likely the enabled fields are missed by mistake here. If so, they should be explicitly fixed separately.
songy23
approved these changes
Sep 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If
enabledis unset in metadata.yaml defaults to false. This commit doesn't change any behavior, it only unblocks the stricter validation open-telemetry/opentelemetry-collector#13921 by setting the false value explicitly.Likely the enabled fields are missed by mistake here. If so, they should be explicitly fixed separately, cc (code owners of the affected components) @nslaughter, @celian-garcia, @ishleenk17, @Caleb-Hurshman, @mrsillydog.