Skip to content

Fix disabling of components#3202

Merged
SanjulaGanepola merged 1 commit into
masterfrom
fix/disable-components
May 21, 2026
Merged

Fix disabling of components#3202
SanjulaGanepola merged 1 commit into
masterfrom
fix/disable-components

Conversation

@SanjulaGanepola

Copy link
Copy Markdown
Member

Changes

This PR is a re-work of #3195. The previous implementation did not actually prevent the component from being installed in the first place as the ConnectionManager is tied to the connection. By the time we connect and disable, the component may already be installed. This PR changes this logic to use the ComponentRegistry to track the set of disabled components instead as this can be done without any connection.

Some associated changes in the other extensions:

How to test this PR

  1. Run the test cases

Checklist

  • have tested my change

Signed-off-by: Sanjula Ganepola <Sanjula.Ganepola@ibm.com>
@github-actions

Copy link
Copy Markdown
Contributor

👋 A new build is available for this PR based on 9a25efe.

@SanjulaGanepola SanjulaGanepola merged commit 47a2a83 into master May 21, 2026
5 checks passed
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