Skip to content
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

The core uses per-domain folder structure #52182

Closed
mshustov opened this issue Dec 4, 2019 · 3 comments
Closed

The core uses per-domain folder structure #52182

mshustov opened this issue Dec 4, 2019 · 3 comments
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mshustov
Copy link
Contributor

mshustov commented Dec 4, 2019

Following #47065
The new platform enforces domain separation for the plugins. At the same time, all core services don't follow the per-domain folder structure.
It creates a situation when:

This issue should evaluate how it's hard it would be to introduce proper per-domain separation and decide whether we want to follow this way at all.

@mshustov mshustov added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Dec 4, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@joshdover joshdover added the stale Used to mark issues that were closed for being stale label Jan 14, 2021
@mshustov mshustov reopened this Mar 30, 2021
@pgayvallet
Copy link
Contributor

This will likely be addressed by #134112

@botelastic botelastic bot removed the stale Used to mark issues that were closed for being stale label Jun 13, 2022
@pgayvallet
Copy link
Contributor

Addressed since the IDM initiative

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants