Skip to content

Conversation

@jack-berg
Copy link
Member

@jack-berg jack-berg commented Jun 24, 2025

Resolves #4374.

We recently cut a release candidate for opentelemetry-configuration. After some additional bake-in time and review, we'd like to cut a stable release.

The stable release needs to coincide with marking key parts of the specification stable, so I'm opening this PR to solicit feedback such that when the time comes, we can mark the specification and opentelemetry-configuration stable is quick succession.

See open-telemetry/opentelemetry-configuration#100 for status of implementations.

cc @open-telemetry/configuration-maintainers

@jack-berg jack-berg requested review from a team June 24, 2025 14:46
@jack-berg
Copy link
Member Author

This is ready for review, but SHOULD not be merged. Assuming we get the required approvals, I'll coordinate merging this with cutting the corresponding release of opentelemetry-configuration.

@github-actions
Copy link

github-actions bot commented Jul 2, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@jack-berg jack-berg removed the Stale label Jul 10, 2025
* `component_provider` - The `ComponentProvider`.
* `type` - The type of plugin interface it provides (e.g. SpanExporter, Sampler,
etc).
* `type` - The type of plugin interface it provides.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not like that in one place we are saying "component" in other "plugin" or "plugin interfaces".
I know that it keeps the same intention, but it makes me harder to read and interpret the specification.
I propose to use the term "Component" everywhere and just mention in the "Component" definition that this is a plugin that allows extensibility of the Configuration SDK.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine with me. I was trying to connect the dots because elsewhere in the spec we both the words component and plugin interface. I'll try to be consistent here with "component" but also have a callout with something to the effect of: "... (also called plugin interface elsewhere in the spec)"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jul 19, 2025
@MrAlias MrAlias removed the Stale label Jul 19, 2025
@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jul 27, 2025
@MrAlias MrAlias removed the Stale label Jul 28, 2025
@github-actions
Copy link

github-actions bot commented Aug 7, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Aug 7, 2025
@MrAlias MrAlias removed the Stale label Aug 7, 2025
@tsloughter
Copy link
Member

A concern I have is that this sort of implies that a spec for the behavior of AutoConfiguredOpenTelemetrySdk.initialize().getOpenTelemetrySdk(); is stable, which I think requires that #4591 be done.

Can the spec of config be stable before SDK initialization is defined?

@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 31, 2025
@lmolkova lmolkova removed the Stale label Oct 31, 2025
@github-actions
Copy link

github-actions bot commented Nov 8, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Nov 8, 2025
@marcalff marcalff removed the Stale label Nov 9, 2025
@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@jack-berg
Copy link
Member Author

The config SIG has been making a lot of progress around the goal of stability and will be looking to stabilize end of 2025 / early 2026. Converting this to a draft until we're ready.

@jack-berg jack-berg marked this pull request as draft November 19, 2025 16:31
@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@jack-berg
Copy link
Member Author

A concern I have is that this sort of implies that a spec for the behavior of AutoConfiguredOpenTelemetrySdk.initialize().getOpenTelemetrySdk(); is stable, which I think requires that #4591 be done.
Can the spec of config be stable before SDK initialization is defined?

@tsloughter I don't understand. AutoConfiguredOpenTelemetrySdk.initialize().getOpenTelemetrySdk() is a java specific concept. How does the declarative config spec imply anything about a java specific concept?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking: Stabilize declarative configuration

10 participants