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

Cannot delete rules or connectors in SO Management #107421

Closed
alexfrancoeur opened this issue Aug 2, 2021 · 6 comments
Closed

Cannot delete rules or connectors in SO Management #107421

alexfrancoeur opened this issue Aug 2, 2021 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@alexfrancoeur
Copy link

In testing out some of the new import / export functionality in 7.14 (#50266) I discovered that I am not able to delete rules or connectors from the SO management UI. Is this expected behavior?

image

The connector is pagerduty and the rule is a logs threshold rule. Export from one environment and imported into another worked flawlessly.

Unrelated (at least, I think it is), I see filters for the old terminology of SO's. Actions & alerts. Is this something we plan to resolve with the terminology switch / migration?

cc: @mikecote @gmmorris @arisonl

@alexfrancoeur alexfrancoeur added the bug Fixes for quality problems that affect the customer experience label Aug 2, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 2, 2021
@mikecote
Copy link
Contributor

mikecote commented Aug 3, 2021

I recall a discussion around deletion in the early discussion of leveraging SO management for alerting import/export. I will defer to @elastic/kibana-core for advice on how to handle the UX for deletion of hidden SO types. From alerting perspective, there are some workflows we would prefer to run (by going through alerting HTTP APIs) but could explore alternate options.

Regarding the filtering, @arisonl opened an issue here: #105575.

@mikecote mikecote added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Aug 3, 2021
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Aug 3, 2021
@ymao1
Copy link
Contributor

ymao1 commented Aug 3, 2021

I believe there was some discussion about allowing deletion of hidden saved object types like rules and connectors in the future, relevant comment here.

@gmmorris
Copy link
Contributor

gmmorris commented Aug 4, 2021

Reading the comment @ymao1 has linked to it sounds like this is something that needs to be done in SOM right? Rather than Alerting code.
Am I reading this correctly? Just want to make sure I'm tagging the issue correctly. :)

@mikecote
Copy link
Contributor

mikecote commented Aug 4, 2021

Forwarding this issue to @elastic/kibana-core team

@mikecote mikecote removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Aug 4, 2021
@lukeelmers
Copy link
Member

I'll go ahead and close this as a duplicate of #106581, where we are discussing how to improve the UX for deleting hidden SOs.

@alexfrancoeur feel free to re-open if there's something which isn't captured in that issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

6 participants