Skip to content

fix(QTDI-1838): register ContainerFinder for studio #1081

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

Merged

Conversation

ozhelezniak-talend
Copy link
Contributor

  • it was removed in 2020 and looks like we've missed it, it was added in a lot of modules for Cloud, but I think by mistake it was removed from component-runtime-manager.

Requirements

  • Any code change adding any logic MUST be tested through a unit test executed with the default build
  • Any API addition MUST be done with a documentation update if relevant

Why this PR is needed?

https://qlik-dev.atlassian.net/browse/QTDI-1838

What does this PR adds (design/code thoughts)?

* it was removed in 2020 and looks like we've missed it, it was added in a lot of modules for Cloud, but I think by mistake it was removed from component-runtime-manager.
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes a missing service registration for the ContainerFinder interface in the component-runtime-manager module. The change restores the StandaloneContainerFinder registration that was accidentally removed in 2020, ensuring proper functionality for studio components.

  • Adds service provider configuration for ContainerFinder interface
  • Registers StandaloneContainerFinder implementation for studio usage
Comments suppressed due to low confidence (1)

component-runtime-manager/src/main/resources/META-INF/services/org.talend.sdk.component.runtime.serialization.ContainerFinder:1

  • The restoration of this service registration should be verified with a test to ensure the ContainerFinder service is properly discoverable and functional. Consider adding a test that validates the service provider mechanism loads the StandaloneContainerFinder correctly.
org.talend.sdk.component.runtime.manager.finder.StandaloneContainerFinder

This comment has been minimized.

@ozhelezniak-talend ozhelezniak-talend requested a review from undx July 29, 2025 09:25
Copy link

sonar-eks bot commented Jul 29, 2025

Passed

Analysis Details

0 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 0 Code Smells

Coverage and Duplications

  • Coverage No coverage information (65.90% Estimated after merge)
  • Duplications No duplication information (1.40% Estimated after merge)

Project ID: org.talend.sdk.component:component-runtime

View in SonarQube

@ozhelezniak-talend ozhelezniak-talend merged commit 0d6756a into master Aug 5, 2025
8 of 9 checks passed
@ozhelezniak-talend ozhelezniak-talend deleted the ozhelezniak/QTDI-1838_correct_isolated_loading branch August 5, 2025 04:21
undx pushed a commit that referenced this pull request Aug 5, 2025
* it was removed in 2020 and looks like we've missed it, it was added in a lot of modules for Cloud, but I think by mistake it was removed from component-runtime-manager.
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