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

[Index Management] Deep link from data streams to ILM #79843

Closed
yuliacech opened this issue Oct 7, 2020 · 1 comment · Fixed by #82165
Closed

[Index Management] Deep link from data streams to ILM #79843

yuliacech opened this issue Oct 7, 2020 · 1 comment · Fixed by #82165
Assignees
Labels
enhancement New value added to drive a business result Feature:ILM Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@yuliacech
Copy link
Contributor

In the Index Management plugin, Data streams tab, when viewing a data stream in a flyout, we need to link managing ILM policy to its edit page in ILM plugin. This can be done with a url generator:

  1. refactor ILM to use 1 central service for routes/navigation
  2. register ulr generator in ILM plugin setup function
  3. use ILM url generator in Index Management as a dependency
@yuliacech yuliacech added enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Oct 7, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:ILM Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants