App Architecture roadmap for New Platform migration

[lukeelmers]

This tracks work for migrating all areas owned by App Architecture team to the New Platform.

Phase I: Move 📦

Shimming and moving code from ui/public and legacy plugins into shims.

7.2

Prep Work

• Delete unused items in ui/public [Migrating away from ui/public #26505] @lizozom
• Move in ui/public that are only imported in one place [Migrating away from ui/public #26505] @lizozom
• Document (re)moved items [Dev Docs entry: Angular removal 7.2 #33289] @lukeelmers + @lizozom
• Initial data plugin framework [Initial framework for data plugin. #34350] @lukeelmers
• Initial embeddables plugin framework [[skip ci] Embeddable API #31941] @stacey-gammon

ui/public modules

• draggable -> moved to ui/vis
• fancy_forms -> moved to vis editor
• filters -> data @lizozom
• modals -> leave behind
• number_list -> moved to agg_types
• query_manager -> deleted @lizozom
• parse_query
• check_box
• debounce
• dirty_prompt
• factories
• icons
• partials
• sortable_column
• table_info
• toggle_button
• toggle_panel
• tooltip

Legacy Plugins

• visualization_editor [[lens] Initial Commit #35627] @wylieconlon @flash1293

7.3

Prep Work

• Initial visualizations plugin framework @lukeelmers [Initial visualizations plugin. #35625]

ui/public modules

• agg_table -> moved into table_vis
• pager -> discover
• pager_control -> discover
• paginated_table -> moved to table_vis
• doc_table -> moved to discover
• doc_viewer -> moved to discover
• utils/parse_es_interval -> data (shim only) [Add dateHistogramInterval utility #39091] @timroes
• apply_filters -> data @lizozom
• filter_bar -> data @lizozom
• filter_manager -> data @lizozom
• query_bar @lizozom
• search_bar -> data @lizozom
• utils/brush_event -> moved to ui/vis/vis_filters @lukeelmers

Legacy Plugins

• markdown_vis -> vis_type_markdown [Markdown vis type np shim #38767] @ppisljar

7.4

ui/public modules

• inspector -> inspector plugin @streamich
• markdown -> kibana-react @lizozom
• timepicker -> kbn_top_nav @lizozom
• kbn_top_nav -> kibana-react [EUIfy Console - partially de-angularize and move custom views out of top_nav #39341][Timelion - move custom views out of top_nav #39518][Reactify Top Nav Menu (kbn_top_nav) #40262][Replace kbn_top_nav with a new React component #39981][[DISCUSS] Top Nav \ Search Bar behavior consistency #41900] @lizozom
• utils/parse_es_interval -> data (remove directory) [[New Platform Migration Phase I]: update dateHisogramInterval & parseEsInterval imports #42917] [[New Platform Migration Phase I]: update dateHisogramInterval & parseEsInterval imports #40553] @alexwizp
• courier -> leave behind @lukasolson
• embeddable -> embeddables [Embeddable migration to NP #40489] @streamich
• error_allow_explicit_index -> leave behind w courier @lukasolson
• index_patterns -> data [typescript indexPatterns service #39247][[New Platform Migration Phase I]: move index patterns to data plugin #40555] @lukeelmers

Legacy Plugins

• timelion -> vis_type_timelion [Convert Timelion to New Platform #38244][[New Platform Migration Phase I]: convert timelion to vis_type_timelion #41667] [[New Platform Migration Phase I]: convert timelion. Migrate server part #43197] [[NP] Timelion #44039] @alexwizp @Avinar-24
• metrics -> vis_type_tsvb [[New Platform Migration Phase I]: convert metrics plugin to vis_type_tsvb #38615][[TSVB] Shim new platform #39169] @alexwizp @Avinar-24 (note: shimming part was done, renaming blocked by Replace TSVB timeseries charts with elastic-charts #33558)
• inspector_views -> inspector [[Inspector Views] [Request View] - Migrate inspector_views to new platform #43191], [[Inspector Views] [Data View] - Migrate inspector_views to new platform #43349] @alexwizp 🚧
• metric_vis -> vis_type_metric [[New Platform Migration Phase I]: convert metric vis to vis_type_metric #41669][[Metric Vis] Shim new platform #42240] @alexwizp 🚧
• region_map -> vis_type_maps region_map [[Region Map] Shim new Platform #40966] [[Region Map] Shim new Platform #40966] @alexwizp @Avinar-24 🚧
• table_vis -> vis_type_table [[New Platform Migration Phase I]: convert table vis plugin to vis_type_table #41248][Convert Data Table Vis to New Platform #38245][[Table Vis] Shim new platform #40732][[New Platform Migration Phase I]: convert table vis plugin to vis_type_table #41248] @alexwizp 🚧
• tagcloud -> vis_type_tagcloud [[New Platform Migration Phase I]: convert tagcloud to vis_type_tagcloud #41249][[Tag Cloud] Shim new platform #42348] @alexwizp 🚧
• tile_map -> vis_type_maps tile_map [[Tile Map] Shim new Platform #41265] [[Tile Map] Shim new Platform #41265] @alexwizp
• vega -> vis_type_vega [Convert Vega to New Platform #38247][[New Platform Migration Phase I]: convert vega plugin to vis_type_vega #39915][[Vega] Shim new platform #40032][[Vega] Shim new platform - Set the correct type for the "Data" dependency #41750][[Vega] Shim new platform - vega_fn.js -> vega_fn.js , use ExpressionFunction #42582] @alexwizp 🚧

7.5

ui/public modules

• timefilter -> data @lizozom 🚧 (moved from 7.4)
• searchsource -> data @lukeelmers @ppisljar (moved from 7.4)
• registry -> deprecate; remove all usages of ui/registry (moved from 7.4)
  • We have about ~7 uiRegistries on our plate left, some of them will be killed in 7.5, others in 7.6
• exit_full_screen -> kibana-react
• autocomplete_providers -> data(<ExitFullScreenButton> 👉 New Platform #42864)
• listen -> copy/leave behind
• indexed_array -> remove, used in uiRegistry, IndexedPatterns, other
• ui/saved_object React components

Legacy Plugins

• interpreter @streamich

7.6

ui/public modules

• vis, vislib, visualize -> visualizations [Initial visualizations plugin. #35625][Prep visualizations plugin for NP migration. #44839] (moved from 7.4)
• management -> management [[New Platform Migration Phase I]: break management out of kibana plugin #38610] @elastic/kibana-app-arch
• share -> NP
• value_suggestions -> data (straight to NP)
• field_wildcard -> data/management or kibana_utils
• storage 👉 src/kibana_utils/storage

7.7

ui/public modules

• management -> advanced settings -> settings

7.x

• Management [[New Platform Migration]: Management - Shim apps #47431] [Management migration to New Platform #47531]

Phase II: Refactor 🛠

Rewiring stateful dependencies, de-Angularizing, Jestifying, TypeScriptifying, NP-readyfying.

• Embeddables
• Expressions
• Filters and Queries
• Index Patterns
• Management App
• Search Deangularize courier/search source #44659 Search 👉 New Platform #42639
• State Management
• Visualizations

Phase III: Cutover 🎉

Moving a plugin from the legacy world to the New Platform—it's when code has moved out of src/legacy and into src/plugins.

AppArch Plugins

• bfetch
• data
  • data.indexPatterns
    • index patterns management UI
      • migration of ui extension points is blocking rollups
  • data.filter
  • data.query
  • data.timefilter
  • data.ui
  • data.search
    • aggs legacy API removal
• dashboard_embeddable_container
• embeddable
• expressions
• inspector
• management
• navigation
• kibana_react
• kibana_utils
  • state management scoped history support [[State Management] State syncing utilities and ScopedHistory #58137]
• ui_actions
• visualizations
• x-pack: advanced_ui_actions
• x-pack: data_enhanced (includes kuery autocomplete)

Other items that need to happen before 8.0

• Miscellaneous "Other" Items Miscellaneous App / Arch items 👉 New Platform #51560
• Migrate App Arch uiSettings [uiSettings]: Migrate items owned by app arch to new platform #63480
• Zoom party 🎉

---

Resources

• WIP: Migration Guide
• New Platform Project
• New Platform Issue: New Kibana platform #9675
• Reference / Example Plugin: [SR] Snapshot and restore plugin boilerplate #32276

[epixa]

If you’re splitting plugins, I recommend splitting oss_telemetry to visualize_telemetry, dashboard_telemetry, etc. as appropriate.

[lizozom]

@elastic/kibana-app-arch we were long discussing where to move kbn_top_nav.

What is it?

kbn_top_nav is a UI component has the following features:

• Displaying the top menu (New, Edit, Help menus etc)
• Extending said menu with custom items using a registry (currently NavBarExtensionsRegistryProvider)
• It currently has an element that can be used to display a inline piece of UI. This option is being used only by DevTools, and these custom pieces should be moved to a flyout and this capability deprecated (@AlonaNadler, @elastic/eui-design )
• Supports adding additional content using $transclude. This is being used to inject things like
  • SearchBar
  • QueryBar
  • Timepicker
  • etc.

Where should it go?

I would like to suggest that kbn_top_nav is a react helper for apps and app developers to create and enrich menus. As such, I believe the new platform implementation should reside in the kibana-react plugin.

[cchaos]

The @elastic/kibana-design team's thoughts around that top menu is to remove it altogether as a component that plugins must extend. We're seeing more and more that each application is using their own style of "menu bar" – for good reason as most plugins are unique.

Instead, what we should provide is more of an established pattern and/or component in EUI. This way, they should all look and behave the same but don't rely on a heavily dictated service within Kibana. The design team can add this to our roadmap for 7.4 as something that should be thought out.

You're welcome to move all those current services to where appropriate but I probably wouldn't put effort into expanding the capabilities.

[streamich]

Migration plans for our main services:

• Embeddables
• Index Patterns
• Expressions
• Visualizations
• State Management
• Filter \ Query \ Timefilter services
• Search