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

[Alerting] Refactor AlertsAuthorization class so it can be reused #98818

Closed
ymao1 opened this issue Apr 29, 2021 · 1 comment · Fixed by #99078
Closed

[Alerting] Refactor AlertsAuthorization class so it can be reused #98818

ymao1 opened this issue Apr 29, 2021 · 1 comment · Fixed by #99078
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete

Comments

@ymao1
Copy link
Contributor

ymao1 commented Apr 29, 2021

In order to support a common RBAC model, we should refactor the AlertsAuthorization class. We can either expose it as a client similar to the alertsClient or expose a library of functions. This will first be used by alerts-as-data RBAC and maybe eventually be used by others.

@ymao1 ymao1 self-assigned this Apr 29, 2021
@ymao1 ymao1 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete labels Apr 29, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants