Repository navigation
show error notification when enabling a provider fails - #208
Merged
iakmc merged 1 commit intoOct 26, 2026
Merged
Conversation
gkrajniak
approved these changes
Oct 23, 2026
Signed-off-by: Iskren <iskren@kubermatic.com>
iakmc
force-pushed
the
fix/marketplace-enable-error-notification
branch
from
October 26, 2026 06:54
679b96a to
6772589
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When enabling a provider fails, for example because the user cannot create APIBindings, the Portal shows no feedback. The modal stays open and the error is only visible in browser dev tools.
installProviderInstancesubscription in the provider detail dialogNotificationService.openErrorStripFIxes
#381
Verification
npm test(26 test files, 228 tests)npx prettier --checkon the changed files