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

[Fleet] Support for UI Extension Points #82478

Closed
paul-tavares opened this issue Nov 3, 2020 · 1 comment · Fixed by #82783
Closed

[Fleet] Support for UI Extension Points #82478

paul-tavares opened this issue Nov 3, 2020 · 1 comment · Fixed by #82783
Assignees
Labels
Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@paul-tavares
Copy link
Contributor

paul-tavares commented Nov 3, 2020

Part of: Integration Specific Policy Views Feature

Description

Expose an interface to other Plugins (that have a dependency on Fleet) that allows them to register a UI extension point which fleet will use when the associated page/view is rendered in the browser. Initial support will include:

  • Support for Integration Details "Custom" view
    This will be a new view that the Integration Details pages will support.
  • Support for Integration Policy Edit View
    A view to be used in the Edit Integration Policy form
  • Support for Integration Policy Create View
    A view to be used in the Create Integration Policy form
@paul-tavares paul-tavares added Team:Fleet Team label for Observability Data Collection Fleet team Team:Defend Workflows “EDR Workflows” sub-team of Security Solution labels Nov 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants