-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Alerting UI] Replaced AppContextProvider introduced by the plugin with KibanaContextProvider #83248
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
[Alerting UI] Replaced AppContextProvider introduced by the plugin with KibanaContextProvider #83248
Conversation
8dab255 to
ee73051
Compare
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
|
Pinging @elastic/uptime (Team:uptime) |
|
@YulNaumenko now it seems to work fine, but when i click create connector is uptime settings, it seems to open flyout twice, there is some flaky behaviour , i will try to post a gif later on. |
gmmorris
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've checked the lazy loading chuck size and the UX throughout Alerts Management and flyouts in solutions and looks like everything is still working as expected. 👍
NVM, I was looking at the Alerts flyout, not the Connectors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Thank you so much for doing this. I tested locally and it seems there are some flaky behavior and an error.
- The edit flyout seems to open and close multiple times when you update credentials:
- When you enter the configuration page of cases it seems that one of the flyouts opens and closes instantly:
- When you press the test tab you get the following error:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for logs and metrics.
shahzad31
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uptime changes LGTM !!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Security Solution changes LGTM! All issues have been resolved! Thank you!
...gers_actions_ui/public/application/components/builtin_action_types/email/email_connector.tsx
Outdated
Show resolved
Hide resolved
...ctions_ui/public/application/components/builtin_action_types/es_index/es_index_connector.tsx
Outdated
Show resolved
Hide resolved
...ons_ui/public/application/components/builtin_action_types/pagerduty/pagerduty_connectors.tsx
Outdated
Show resolved
Hide resolved
...s_ui/public/application/components/builtin_action_types/servicenow/servicenow_connectors.tsx
Outdated
Show resolved
Hide resolved
...ers_actions_ui/public/application/components/builtin_action_types/slack/slack_connectors.tsx
Outdated
Show resolved
Hide resolved
...ers_actions_ui/public/application/components/builtin_action_types/teams/teams_connectors.tsx
Outdated
Show resolved
Hide resolved
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Distributable file count
Page load bundle
History
To update your PR or re-run it, just comment with: |
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |




Current PR include the next changes:
useKibana().serviceskibana_react.mock. Unit tests code reduced and simplified.Resolve #65146