Skip to content

fix: use plugin UI SDK in plugin UIs#18

Merged
adityathebe merged 2 commits into
mainfrom
fix/arthas-plugin-ui-sdk
May 20, 2026
Merged

fix: use plugin UI SDK in plugin UIs#18
adityathebe merged 2 commits into
mainfrom
fix/arthas-plugin-ui-sdk

Conversation

@adityathebe
Copy link
Copy Markdown
Member

@adityathebe adityathebe commented May 20, 2026

Arthas and Inspektor Gadget UIs were using hand-rolled plugin operation URLs, which can break under the Mission Control plugin UI proxy.

Vendor the built plugin UI SDK until it is published to npm, and use its invoke helper for operations.
Also signal tab readiness through the SDK after each UI renders.

Arthas UI was constructing plugin operation URLs by hand, which can break when served through the Mission Control plugin UI proxy.

Vendor the built plugin UI SDK as a local dependency, use its invoke helper for operations, and signal tab readiness after render.
Inspektor Gadget UI was constructing plugin operation URLs by hand, which can break when served through the Mission Control plugin UI proxy.

Vendor the built plugin UI SDK as a local dependency, use its invoke helper for operations, and signal tab readiness through the SDK.
@adityathebe adityathebe changed the title fix: use plugin UI SDK in Arthas UI fix: use plugin UI SDK in plugin UIs May 20, 2026
@adityathebe
Copy link
Copy Markdown
Member Author

@coderabbitai review

@adityathebe adityathebe merged commit de72178 into main May 20, 2026
23 checks passed
@adityathebe adityathebe deleted the fix/arthas-plugin-ui-sdk branch May 20, 2026 16:10
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.

1 participant