[RAM] 142183 create bulk delete on rules

[guskovaue]

Connected with: #142183

Summary

I am working on getting alive bulk delete for rules.

I this PR I've created a new internal endpoint _bulk_delete.
This endpoint is getting rules ids or filter as parameter and return object like this: { errors: [], total }.

Decide to stick with only backend because PR is already pretty big. But I've tested it from UI as well.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[guskovaue]

I just tried via POSTMAN to issue a PATCH command to https://localhost:5601/internal/alerting/rules/_bulk_delete with an empty request body and saw all of my rules deleted when I was expecting to get an error message telling me I need to specify ids or a filter.

@ymao1 Yes, I see now! It's bad. I've tested sending no arguments, but I think I did not have any rules in my account, so I received an error.
Sorry for that. Here I've fixed it and wrote more test to check this part of validation: 40e7fd1

[ymao1]

Verified the latest changes and bulk deleting via POSTMAN works as expected. There is still a question of what the task manager bulkRemoveIfExists should return if some tasks are deleted and some error and we need to handle any potential errors from taskManager.bulkRemoveIfExists in the rules client so we do not introduce the possibility of Unhandled promise rejections.

[guskovaue]

@elasticmachine merge upstream

[ymao1]

LGTM. Thanks for the latest updates! Approving to unblock :)

I left one comment here about not needing to check for ensureRuleTypeEnabled during bulk delete (we don't check for it during normal delete so I don't think it's needed for bulk delete?)

Also would like to see functional tests for the new task manager functions in x-pack/test/plugin_api_integration/test_suites/task_manager/task_management.ts but I'm fine with that being done as a followup.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f558ab2

Metrics [docs]

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
alerting	24	26	+2

History

• 💔 Build #82467 failed c482fc3
• 💔 Build #82420 failed 9f32f95bb198f9774806bb5787956e691d424925
• 💚 Build #82216 succeeded e340ee2
• 💚 Build #82000 succeeded 4652756
• 💔 Build #81998 failed f84fdde
• 💔 Build #81997 failed d08f2f6

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @guskovaue