-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Meta] Migrate Kibana plugins to TS project references #80508
Comments
@restrry for our planning purposes, is there a target release or deadline for this effort? ty |
To support project references. References elastic#80508.
* Add TS config for kibana_legacy To support project references. References #80508.
* Add TS config for kibana_legacy To support project references. References elastic#80508.
Also add missing pieces to kibana_react, as a follow-up to elastic#80992. References elastic#80508 References elastic#81003
@ryankeairns @timroes |
Ack @restrry -- we're sorting out how we want to handle the changes required for |
Also add missing pieces to kibana_react, as a follow-up to elastic#80992. References elastic#80508 References elastic#81003 # Conflicts: # tsconfig.json
@restrry According to the docs migration order matters, so plugins at the leaves of the dependency tree won't be able to begin migration until their dependencies have been migrated. Because of the sequential nature of this work, I'd like to set expectations. There are 6 weeks until feature freeze, and ES UI's apps have many unmigrated dependencies. For example, here are Index Management's dependencies:
Looking at how many dependencies remain to be migrated and how much time remains in the dev cycle, it seems likely that we'll be unblocked with a week or two remaining. This is also typically the time when we're focused on polishing and testing new features in preparation for feature freeze. Sometimes we uncover bugs or opportunities for improvement that we need to execute on in order to ship. With this in mind, i think there's a high probability that some percentage of ES UI's apps (~75%) won't be migrated to TS projects by 7.11 feature freeze. |
It's also very likely that the security team's plugins won't be migrated either, as we first have to resolve the circular dependency between security and spaces. I've been working on a POC for this, but time has not been on my side this week. And based on CJ's list ^, we are one of the teams blocking their work. I am rather surprised that Index Management has a dependency on the spaces plugin though. Is that transient by way of another dependency? |
@legrego Yes, it's a transient dependency. Here's the package.json. It has an optional dependency upon |
Index Pattern Management is done and merged folks! |
References elastic#80508. References elastic#81003. # Conflicts: # x-pack/tsconfig.refs.json
Observability (#89320) is done. |
ML (#90021) is done. |
Infra (#90118) is done. |
KibanaApp should be done as well in case I didn't forget a plugin (we own way too many) |
@flash1293 |
Uptime (#90510) is done. |
Fleet (#82220) is ✅ |
@restrry It seems like those belong to app-services. |
@flash1293 my bad! |
|
|
APM is done. |
Monitoring is done. |
Documentation
Preparatory work #46773
Security Solution team
Blockers: ✅ Circular dependency between
security_solution
<-->lists
#80513Blockers: ✅ Circular dependency between
actions
<-->lists
Blockers: ✅ Circular dependency between
security_solution
<-->fleet
#91111@elastic/siem
@elastic/endpoint-app-team
App team
@elastic/kibana-app
Issue #84750
charts
<-->expressions
charts
<-->vis_default_editor
[Visualizations] Remove charts - editor plugins cyclic dependencies #84887vis_default_editor
<-->visualizations
vis_default_editor
<-->visualize
visualizations
<-->visualize
AppServices team
Blockers:
data
<-->expressions
Remove circular dependency between data & expressions plugins #80510uiActions
<-->embeddable
uiActions
<-->data
Remove circular dependency between uiActions & data/embeddable plugins #82047uiActions
<-->embeddable
Remove circular dependency between uiActions & data/embeddable plugins #82047@elastic/kibana-app-services
APM team
apm
<-->infra
(Remove circular dependecy between apm and infra #89739)@elastic/apm-ui
Presentation team
@elastic/kibana-presentation
Conversion draft PR: #86019
Core team
@elastic/kibana-core
Core UI team
@elastic/kibana-core-ui
Logs metrics UI team
@elastic/logs-metrics-ui
Fleet
@elastic/fleet
Observability UI team
@elastic/observability-ui
Stack monitoring UI team
@elastic/stack-monitoring-ui
Uptime team
@elastic/uptime
ML team
@elastic/ml-ui
Maps team
@elastic/kibana-gis
maps_legacy
<-->region_map
Remove circular depencency between maps_legacy and region_map and tile_map plugins #88265maps_legacy
<-->tile_map
Remove circular depencency between maps_legacy and region_map and tile_map plugins #88265Operations team
@elastic/kibana-operations
Security team
Blockers:⚠️ Circular dependency between (resolved via #81891)security
<-->spaces
#80496@elastic/kibana-security
Kibana telemetry team
@elastic/kibana-telemetry
Kibana Alerting team
@elastic/kibana-alerting-services
Enterprise Alerting team
@elastic/enterprise-search-frontend
Elasticsearch UI team
Blockers: ✅
Circular dependency between
(fixed in #89739)infra
<-->apm
<-->infra
forcross_cluster_replication
,index_lifecycle_management
,index_management
,remote_clusters
,rollup
Track progress here: #89321
@elastic/es-ui
Logstash team
@elastic/logstash
Reporting team
@elastic/kibana-reporting-services
security-asset-management
@elastic/security-asset-management
The text was updated successfully, but these errors were encountered: