-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Alerting] Fixing broken Alerts view when no Global All Kibana privilege #88727
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
Conversation
x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/home_page.ts
Show resolved
Hide resolved
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
YulNaumenko
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.
LGTM!
mikecote
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.
Changes LGTM 👍
rashmivkulkarni
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.
LGTM
x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/home_page.ts
Show resolved
Hide resolved
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
…ege (elastic#88727) * Making kibanaFeatures an optional parameter and catching error on plugin start * Gracefully handle 404 errors when no access to features endpoint * Adding functional test
…ege (elastic#88727) * Making kibanaFeatures an optional parameter and catching error on plugin start * Gracefully handle 404 errors when no access to features endpoint * Adding functional test # Conflicts: # x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/home_page.ts
… privilege (#88727) (#88781) * [Alerting] Fixing broken Alerts view when no Global All Kibana privilege (#88727) * Making kibanaFeatures an optional parameter and catching error on plugin start * Gracefully handle 404 errors when no access to features endpoint * Adding functional test # Conflicts: # x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/home_page.ts * Fixing linting Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Resolves #88624
Summary
Wrapping the
getFeatures()API call in a try/catch block to catch 404 errors that arise when a user doesn't have the permissions to access that API.Checklist
Delete any items that are not applicable to this PR.