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

It isn't possible to reuse a single connector across multiple actions #70083

Closed
gmmorris opened this issue Jun 26, 2020 · 4 comments
Closed

It isn't possible to reuse a single connector across multiple actions #70083

gmmorris opened this issue Jun 26, 2020 · 4 comments
Labels
DX Issues related to Developer Experience estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Project:MoreConnectors Alerting team project for integrating with more external services. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gmmorris
Copy link
Contributor

This is a step towards addressing #69442

Make it possible for an ActionType (which by that point might be a ConnectorType) to register multiple executors each of which represents a potential kind of action that might be taken using the connector.

@azasypkin azasypkin added Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 29, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor

Moving from 7.12 - Candidates to 7.x - Candidates.

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@gmmorris gmmorris added NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Project:MoreConnectors Alerting team project for integrating with more external services. Feature:Actions/Framework Issues related to the Actions Framework labels Jun 30, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added DX Issues related to Developer Experience estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@mikecote
Copy link
Contributor

mikecote commented May 4, 2023

We'll go ahead and close this issue, we now have the sub-actions framework that @cnasikas developed that enables this capability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX Issues related to Developer Experience estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Project:MoreConnectors Alerting team project for integrating with more external services. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

4 participants