Skip to content

use correct config provider#101

Closed
zeitlinger wants to merge 2 commits intotrask:declarative-config/spring-step-onefrom
zeitlinger:fix-spring-config-provider
Closed

use correct config provider#101
zeitlinger wants to merge 2 commits intotrask:declarative-config/spring-step-onefrom
zeitlinger:fix-spring-config-provider

Conversation

@zeitlinger
Copy link
Copy Markdown

No description provided.

Runtime.getRuntime().addShutdownHook(new Thread(sdk::close));
logStart();
return sdk;
return new SpringOpenTelemetrySdk(sdk, SpringConfigProvider.create(model));
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

since we're already converting the yaml into declarative config model above (in order to support DeclarativeConfigurationCustomizers), why do it again in SpringConfigProvider?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I think the type coersion was needed.
I may have been wrong - but then we should remove spring config provider altogether.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

good point, I've removed the spring config provider

@zeitlinger zeitlinger closed this Jan 6, 2026
@zeitlinger zeitlinger deleted the fix-spring-config-provider branch January 6, 2026 16:40
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.

2 participants