-
Notifications
You must be signed in to change notification settings - Fork 205
Allows API packages to specify file-based and env-based config #1621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
} | ||
use function interface_exists; | ||
|
||
interface_exists(ComponentPlugin::class); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting 👀
Generally curious as I have not seen this before: does this differ in some way to extending OpenTelemetry\API\Configuration\Config\ComponentPlugin
on this interface?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extending would lead to BC breaks, for example we cannot narrow the type of ComponentProvider::getConfig()
$registry
from API
ComponentProviderRegistry
to SDK
ComponentProviderRegistry
.
Should I base #1523 on the back of this, given the environment changes here? 🤔 (I appreciate that my PR is a little stale, but I plan to pick it up again in future) |
Moves
ComponentProvider
and related classes to API and adds env-based loader to allow API packages (instrumentations and propagators) to specify their configuration options.