-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Reporting] Replace Job Completion Notifier as NP Plugin #47283
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
[Reporting] Replace Job Completion Notifier as NP Plugin #47283
Conversation
b0000e9 to
a2990a6
Compare
39d29ea to
0894f7c
Compare
|
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
9effb88 to
a388775
Compare
a388775 to
12ef096
Compare
12ef096 to
366408d
Compare
💚 Build Succeeded
|
💚 Build Succeeded |
💚 Build Succeeded |
| method: 'GET', | ||
| config: getRouteConfig(), | ||
| handler: (request: Request) => { | ||
| // @ts-ignore |
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.
Unrelated cleanup of TS
💚 Build Succeeded |
💔 Build Failed |
bmcconaghy
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.
Code LGTM. I would recommend getting someone from @elastic/kibana-platform to review this too.
|
|
||
| public setup(core: CoreSetup) {} | ||
|
|
||
| // FIXME: only perform these actions for authenticated routes |
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.
How does this behave now? Will it throw errors when unauthenticated?
💚 Build Succeeded |
joshdover
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.
Should the reporting_notifier be a separate plugin than reporting? It seems to me we'd want xpack.reporting.enabled=false config to also disable this piece. Other than that, LGTM
💔 Build Failed |
💚 Build Succeeded |
💚 Build Succeeded |
* [Reporting] Replace Job Completion Notifier as NP Plugin * beautiful toasts * unit test * showNotifications returns observable * fix kibana.json * depends on links * no prettier ignore * Update content per feedback * Remove unnecessary wrapper * remove type annos and condense * use an observable of the stop method * rename the new platform plugin to match legacy * fix i18n config * additional plugin rename * i18n strings prefix change * try something with x-pack/.i18nrc.json * remove a few more notifier phrasing from plugin definition
…8703) * [Reporting] Replace Job Completion Notifier as NP Plugin * beautiful toasts * unit test * showNotifications returns observable * fix kibana.json * depends on links * no prettier ignore * Update content per feedback * Remove unnecessary wrapper * remove type annos and condense * use an observable of the stop method * rename the new platform plugin to match legacy * fix i18n config * additional plugin rename * i18n strings prefix change * try something with x-pack/.i18nrc.json * remove a few more notifier phrasing from plugin definition
|
|
||
| public setup(core: CoreSetup) {} | ||
|
|
||
| // FIXME: only perform these actions for authenticated routes |
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.
Follow up note: this can be possibly be achieved better by registering the job completion notifier as a component of something global for authenticated screens in Kibana, such as the nav header. This is what the Newsfeed Service does, and it is effectively prevented from fetching for news on the Login page due to there being no Nav Header on the Login page.
Summary
Closes #45427
This PR replaces the Reporting Job Completion Notifier hack with New Platform plugin to run on the background of every page.
[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] Documentation was added for features that require explanation or tutorials[ ] This was checked for keyboard-only and screenreader accessibility[ ] License checking[ ] Only run the poller on authenticated pages