This PR migrates the vast majority of Alerting legacy code to the Kibana Platform.
This includes:
1. Removed legacy Task Manager
2. Migrates Fixture plugins in Alerting, Triggers UI and Task Manager Perf
This does not includes:
1. The PagerDuty simulator due to a lack of support for custom responses in the platform. issue opened. https://github.com/elastic/kibana/issues/65045
2. The Webhooks simulator due to a lack of support for custom authorisation. Requires investigation.
* feat(NA): added new build step to generate a static file system for node_modules and monkey patch the bin start files to include the static file system loader on begining.
* chore(NA): updated lockfile.
* chore(NA): replace import to the correct static-fs files.
* fix(NA): resolve for a correct static fs loader.
* chore(NA): last static-fs working version.
* feat(NA): changed patched entryPoints.
* chore(NA): update to last static fs.
* fix(NA): fix imports on webpack shims. chore(NA): added new static-fs version.
* chore(NA): update to static-fs with stat and statSync.
* fix(NA): vendor chunk filtering in order to include default node modules and static node modules.
* refact(NA): major refact on create static modules fs task.
* fix(NA): remove global from clean empty folders task.
* chore(NA): change args order for deleteAll.
* chore(NA): move to the new static fs
* feat(NA): migrate to last apis of static fs
* fix(NA): patch correct entry file.
* chore(NA): last stable integration with static-fs task
* chore(NA): rollback some unecessary changes
* chore(NA): remove changes on sinon webpackshim
* chore(NA): integrate with official static-fs version
* chore(NA): integrate last thread-loader version
* chore(NA): added last static-fs version
* chore(NA): upgrade to last static-fs version
* chore(NA): upgrade to last static-fs version 1.1.1
* chore(NA): rever static-fs version to 1.1.0
* chore(NA): upgrade static-fs to 1.1.1
* chore(NA): upgrade static-fs for last 1.2.0 version
* chore(NA): update package.json
* chore(NA): run apm after patched environment
* chore(NA): specify rule to disable eslint for
* chore(NA): remove changes in the src/apm file
* chore(NA): change apm order in the dev scripts
* chore(na): update static-fs versin
* chore(NA): bump static fs version
* chore(NA): correctly lint task file
* chore(NA): move away from rimraf to del
* chore(NA): bump static-fs version
* chore(NA): bump static-fs version
* chore(NA): bump static-fs version
* chore(NA): bump static-fs version
* chore(NA): bump to last static-fs version
* chore(NA): apply changed according PR review feedback
* chore(NA): remove changes to base optimizer
* chore(NA): fix discover pattern
* chore(NA): bump static-fs version
* chore(NA): bump static fs to 1.6.3
* chore(NA): bump static-fs to 1.6.4
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs to last version
* chore(NA): bump static-fs for 1.8.3
* chore(NA): bump static-fs to 1.9.0
* chore(NA): bump static-fs to 1.9.1
* chore(NA): update to last static-fs version 1.10.0
* chore(NA): moving to @elastic/static-fs package
* fix(NA): change import to the new package
* chore(NA): bump elastic static-fs to 1.0.1
Co-authored-by: spalger <email@spalger.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Add set-value as an explicit dependency
This is a more robust solution than lodash's set().
* Replace lodash.set() with set-value's equivalent
* Rebuild renovate config
We added set-value to our dependencies.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Move SIEM public/ folder to NP plugin
This is solely renames; fixes come next.
* Update relative imports in our API tests
* Fix linter errors following move to NP folder
These paths got a little shorter, so some lines could be collapsed.
* Move client dependencies to NP package.json
I'm removing the @types/js-yaml for now because I'm not sure we need it;
I'll add it back later if we do.
* Fix relative imports to other plugins
* Fix errant uses of ui/chrome
* Remove legacy plugin shim
* Move feature registration into plugin
This previously had to be part of legacy bootstrapping due to an order
of operations issue.
* Disconnect legacy plugin
The index file should now be redundant with what's in the plugin:
* app registration
* feature registration
* Move public gitattributes
* Remove references to legacy embeddables
We can now use the NP API. Maps embeddable will not work here until
their work is merged, but this should prevent us from importing legacy
code and thus breaking the build.
* Add our frontend dependencies to kibana.json
These are all required for now, because that's how they're typed. If
they _should_ be optional (and I think several should), we need to
update the type and handle the null case within the app.
* Replace use of ui/new_platform mocks in embeddable utils
* Fix remaining jest tests
* Replace build-breaking ui/new_platform mocks with equivalents in core
proper
* Remove unnecessary mocks of ui/new_platform
* Remove references to legacy SIEM folder
* I left the reference in CODEOWNERS in case someone tries to sneak
something back
* I left the .gitignore reference for the same reason
* Fix mocks of relative paths
These were not caught by typescript and were causing test failures.
* Export our client plugin contracts
They're empty for now.
* Move from deprecated appmount API
The new one dropped a param we weren't using.
* Add missing mock causing test failures
* Don't re-export core types from our plugin
Import them from core where we need them, instead
* Move Actions UI registry outside of mount
This is already imported, there's no benefit (and potential timing
issues) with doing this inside the mount.
* Add security's setup contract to our StartServices
This doesn't change what's used, only how we're typing it. The types are now a
little more truthful as:
* our StartPlugins don't include setup contracts
* our StartServices includes everything we use at Start time, including
the one setup plugin.
* Add order and icon back to the sidebar link
* Replace plugin class properties with constants
These are shared, and should be consistent.
* Enable our UI on NP
* Add missed plugin dependencies
We're not using their contracts, but we are importing code from them.
* Revert use of constant in translation
Can't do that, whoops
* i18n our feature catalogue entry
* Remove unnecessary array from single element
* Remove unused keys
These were the legacy translations used... well, I don't know where they
were used.
* Ignore circular dependencies in external plugins
* Normalize exclusions
* Add undeclared dependencies to kibana.json
We import our maps embeddable from maps, and we pass inspector to the
embeddable. I just missed these in my audit. This was causing errors in
the map embeddable.
* Await our call to setLayerList
This is an async call that we need to complete before we can render.
* Reduce siem plugin size
When we load our initial plugin (before our app is loaded), were were
implicitly importing all of kibana_react with this import. While a
global module prevents this from affecting our bundle size currently,
that could change in the future. Since we only need a reference to our
class, we just import that instead.
* chore(NA): reduce siem bundle size using babel-plugin-transform-imports for lodash
* fix(NA): dont use preventFullImport
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* snapshot updates
* bump to eui 22.3.0
* snapshots
* Fix css selector in test to match EUI internal DOM change
* Updated snapshots
* Insert react-beautiful-dnd@10 into top-level kibana to force siem's node_modules to hold its correct version
* More snapshot updates, resolved a typescript issue
* Move react-beautiful-dnd dependency around to make things happy again
* Use SearchFilterConfig from the top-level eui export
* Swallow 'ResizeObserver error does not have an err object' error in canvas
* Swallow ResizeObserver error cross-browser
* bump dependency, add edge support in ftr services
* add config files
* fix browser version for msedge
* use npm ms-chromium-edge-driver
* download edge driver aside from session creation
* move dependency to dev
* update dist/index file
* bump edge-driver version
* change type to msedge to match w3c spec
* fix discover tests for Edge
* Revert "fix discover tests for Edge"
This reverts commit 87e7fdd256.
* bump driver version up
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* update crypto packages
* as type for return value
* get default export
* add if checks
* wrap errors in i18n
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [kbn/ui-shared-deps] expand and split
* add two import styles for eui/react-dom that are new
Co-authored-by: spalger <spalger@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
