Skip to content

[Alerting v2] Split action policies APIs#280238

Open
cnasikas wants to merge 33 commits into
elastic:mainfrom
cnasikas:alerting_v2_bulk_apis_action_policies
Open

[Alerting v2] Split action policies APIs#280238
cnasikas wants to merge 33 commits into
elastic:mainfrom
cnasikas:alerting_v2_bulk_apis_action_policies

Conversation

@cnasikas

@cnasikas cnasikas commented Jul 22, 2026

Copy link
Copy Markdown
Member

Summary

Same as #277616, this PR splits the generic bulk action policy APIs into multiple bulk action APIs per operation. This makes the Rules and Action Policies APIs consistent with the same responses. It also aligns the response schema for the bulk alert action API.

Fixes: https://github.com/elastic/rna-program/issues/364
Fixes: https://github.com/elastic/rna-program/issues/352

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

@cnasikas cnasikas self-assigned this Jul 22, 2026
@cnasikas cnasikas added the release_note:skip Skip the PR/issue when compiling release notes label Jul 22, 2026
@cnasikas cnasikas added backport:skip This PR does not require backporting Team:ResponseOps Platform ResponseOps team (formerly the Cases and Alerting teams) t// Feature:AlertingV2 v9.6.0 labels Jul 22, 2026
@cnasikas cnasikas changed the title [Alerting v2] Reshape action policies APIs [Alerting v2] Split action policies APIs Jul 22, 2026
@cnasikas
cnasikas marked this pull request as ready for review July 23, 2026 09:51
@cnasikas
cnasikas requested a review from a team as a code owner July 23, 2026 09:51
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/response-ops (Team:ResponseOps)

@kibanamachine kibanamachine added the reviewer:scout Agentic PR Scout test review label Jul 23, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the action-policy bulk API split. The server refactor (per-action by-ID endpoints, shared BulkResponse shape, canonical bulk-error mapping) and its unit + Scout coverage look solid. One concrete issue: the _bulk_action (alert actions) response contract change was not propagated to the alert-episodes UI consumer, which will break the bulk-action toasts. Flagged inline.

Generated by Claude Reviewer for #280238 · 600.1 AIC · ⌖ 11.8 AIC · ⊞ 4.6K

@cnasikas

Copy link
Copy Markdown
Member Author

@elasticmachine merge upstream

@kibanamachine

Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Scout Lane #10 - stateful-classic / default / local-stateful-classic - Entity attachment cases – flyout add-to-case actions and Entities accordion - Entities accordion renders when entity attachments were added via API
  • [job] [logs] Scout Lane #10 - stateful-classic / default / local-stateful-classic - Entity attachment cases – flyout add-to-case actions and Entities accordion - renders no Entities accordion when a case has no entity attachments

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
alertingVTwo 1.3MB 1.3MB +1.4KB
securitySolution 13.6MB 13.6MB +31.0B
total +1.4KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
alertingVTwo 26.0KB 26.6KB +603.0B
securitySolution 190.5KB 190.5KB +8.0B
total +611.0B

History

cc @cnasikas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting Feature:AlertingV2 release_note:skip Skip the PR/issue when compiling release notes reviewer:scout Agentic PR Scout test review Team:ResponseOps Platform ResponseOps team (formerly the Cases and Alerting teams) t// v9.6.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants