Use consistent vocabulary in reference to components and plugins #4806
Conversation
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
jack-berg
commented
Dec 15, 2025
| The [configuration data model](./data-model.md) SHOULD support configuration of | ||
| all SDK extension plugin interfaces. SDKs SHOULD | ||
| support [registration](#register-componentprovider) of custom implementations of | ||
| SDK extension plugin interfaces via the `ComponentProvider` mechanism. |
Member
Author
There was a problem hiding this comment.
Moved up so all the normative language is centralized, leaving this section to just connect the dots of how plugin components are mapped.
…y-specification into consistent-component-vocabulary
carlosalberto
approved these changes
Dec 18, 2025
|
This PR was marked stale. It will be closed in 14 days without additional activity. |
codeboten
reviewed
Jan 5, 2026
…y-specification into consistent-component-vocabulary
robsunday
reviewed
Jan 7, 2026
| * [Create Plugin](#create-plugin) | ||
| + [PluginComponentProvider](#plugincomponentprovider) | ||
| - [Supported SDK plugin components](#supported-sdk-plugin-components) | ||
| - [PluginComponentsProvider operations](#plugincomponentsprovider-operations) |
There was a problem hiding this comment.
Suggested change
| - [PluginComponentsProvider operations](#plugincomponentsprovider-operations) | |
| - [PluginComponentProvider operations](#plugincomponentprovider-operations) |
| | [log record processor](../logs/sdk.md#logrecordprocessor) | [LogRecordProcessor](https://github.com/open-telemetry/opentelemetry-configuration/blob/main/schema-docs.md#logrecordprocessor-) | | ||
|
|
||
| ##### ComponentsProvider operations | ||
| ##### PluginComponentsProvider operations |
There was a problem hiding this comment.
Suggested change
| ##### PluginComponentsProvider operations | |
| ##### PluginComponentProvider operations |
| ##### ComponentsProvider operations | ||
| ##### PluginComponentsProvider operations | ||
|
|
||
| The `ComponentsProvider` MUST provide the following functions: |
There was a problem hiding this comment.
Suggested change
| The `ComponentsProvider` MUST provide the following functions: | |
| The `PluginComponentProvider` MUST provide the following functions: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In response to this feedback: #4568 (comment)
The declarative config SDK spec uses "component", "extension plugin interface", "SDK extension plugins" somewhat interchangeable.
This PR makes the vocabulary consistent:
To facilitate, this PR:
ComponentProvidertoPluginComponentProvider. This makes it clear that only plugins are being provided rather than all components.ComponentProvider.createPlugintoPluginComponentProvider.createComponent.There are no functional changes in this PR, just naming updates.