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.

Sign up for GitHub

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

Jump to bottom

Document the way new platform is integrated into legacy one #14870

Closed
kimjoar opened this issue Nov 9, 2017 · 1 comment
Closed

Document the way new platform is integrated into legacy one #14870

kimjoar opened this issue Nov 9, 2017 · 1 comment
Assignees
@azasypkin
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kimjoar
Copy link
Contributor

kimjoar commented Nov 9, 2017

We should add a readme to ./platform/legacy that explains how the legacy feature works, e.g. how we let the new platform's http server own the port and how it forwards to old platform.
@kimjoar kimjoar added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Jan 24, 2018
@epixa
Copy link
Contributor

epixa commented May 5, 2018

cc @azasypkin in case you want to handle this in conjunction with #12660

@kimjoar kimjoar mentioned this issue May 7, 2018
Closed
10 tasks
@azasypkin azasypkin mentioned this issue Jun 21, 2018
Merged
@azasypkin azasypkin changed the title Add readme for legacy feature in new platform Document the way new platform is integrated into legacy one Jun 29, 2018
@azasypkin azasypkin self-assigned this Jun 29, 2018
@azasypkin azasypkin mentioned this issue Jul 18, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azasypkin azasypkin

Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kimjoar @epixa @azasypkin