Skip to content

[Cases][AttachmentV2] Remove actions in open api docs#265141

Merged
christineweng merged 2 commits intoelastic:mainfrom
christineweng:cases-remove-actions-in-openapi-and-safe-parse
Apr 23, 2026
Merged

[Cases][AttachmentV2] Remove actions in open api docs#265141
christineweng merged 2 commits intoelastic:mainfrom
christineweng:cases-remove-actions-in-openapi-and-safe-parse

Conversation

@christineweng
Copy link
Copy Markdown
Contributor

@christineweng christineweng commented Apr 22, 2026 •
edited by kibanamachine
Loading

Summary

Reverts Actions related docs because it will be deprecated post attachment V2 migrations.

Checklist

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

@christineweng christineweng self-assigned this Apr 22, 2026
@christineweng christineweng requested a review from a team as a code owner April 22, 2026 19:47
@christineweng christineweng added release_note:skip Skip the PR/issue when compiling release notes backport:version Backport to applied version labels Team:Cases Security Solution Cases team v9.4.0 v9.5.0 labels Apr 22, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Apr 22, 2026

Pinging @elastic/kibana-cases (Team:Cases)

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod Bot requested a review from a team as a code owner April 22, 2026 20:20
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Apr 22, 2026

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #70 / Entity Analytics - Risk Score Maintainer @ess @serverless @serverlessQA Asset Criticality CSV Upload V2 "after all" hook for "should handle all errors in the csv"
  • [job] [logs] FTR Configs #70 / Entity Analytics - Risk Score Maintainer @ess @serverless @serverlessQA Asset Criticality CSV Upload V2 "before all" hook for "uploads CSV and updates asset criticality for a matched entity"
  • [job] [logs] affected Scout: [ observability / synthetics ] plugin / local-stateful-classic - FilterMonitors - filters monitors by tags with AND/OR logic

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
cases 2.3MB 2.3MB -601.0B

cc @christineweng

@christineweng christineweng force-pushed the cases-remove-actions-in-openapi-and-safe-parse branch from 84265d0 to 34e5cdb Compare April 23, 2026 17:06
@christineweng christineweng changed the title [Cases][AttachmentV2] Remove actions in open api docs and add safe parse [Cases][AttachmentV2] Remove actions in open api docs Apr 23, 2026
janmonschke
janmonschke approved these changes Apr 23, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@janmonschke janmonschke left a comment

Choose a reason for hiding this comment

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

Thanks for cleaning this up 👍

@christineweng christineweng enabled auto-merge (squash) April 23, 2026 18:07
@christineweng christineweng merged commit 4bc553b into elastic:main Apr 23, 2026
11 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 23, 2026

Starting backport for target branches: 9.4

https://github.com/elastic/kibana/actions/runs/24856742362

@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Apr 23, 2026

💔 All backports failed

Status Branch Result
❌ 9.4 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.4:
- [Cases][Docs] - Add additional examples and cleanup to openApi (#263617)

Manual backport

To create the backport manually run:

node scripts/backport --pr 265141

Questions ?

Please refer to the Backport tool documentation

@christineweng christineweng mentioned this pull request Apr 24, 2026
Merged
@christineweng
Copy link
Copy Markdown
Contributor Author

christineweng commented Apr 24, 2026

💚 All backports created successfully

Status Branch Result
✅ 9.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

christineweng added a commit that referenced this pull request Apr 24, 2026
@christineweng
[9.4] [Cases][AttachmentV2] Remove actions in open api docs (#265141) (…
bb1f7e8 
…#265423)

# Backport

This will backport the following commits from `main` to `9.4`:
- [[Cases][AttachmentV2] Remove actions in open api docs
(#265141)](#265141)

<!--- Backport version: 11.0.2 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-04-23T20:17:19Z","message":"[Cases][AttachmentV2]
Remove actions in open api docs (#265141)\n\n## Summary\n\nReverts
`Actions` related docs because it will be deprecated post\nattachment V2
migrations.\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4bc553ba6b2c2499b3e1177d357fb7ea4ecf1367","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Team:Cases","v9.4.0","v9.5.0"],"title":"[Cases][AttachmentV2]
Remove actions in open api
docs","number":265141,"url":"https://github.com/elastic/kibana/pull/265141","mergeCommit":{"message":"[Cases][AttachmentV2]
Remove actions in open api docs (#265141)\n\n## Summary\n\nReverts
`Actions` related docs because it will be deprecated post\nattachment V2
migrations.\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4bc553ba6b2c2499b3e1177d357fb7ea4ecf1367"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/265141","number":265141,"mergeCommit":{"message":"[Cases][AttachmentV2]
Remove actions in open api docs (#265141)\n\n## Summary\n\nReverts
`Actions` related docs because it will be deprecated post\nattachment V2
migrations.\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4bc553ba6b2c2499b3e1177d357fb7ea4ecf1367"}}]}]
BACKPORT-->
rbrtj pushed a commit to walterra/kibana that referenced this pull request Apr 27, 2026
@christineweng @kibanamachine @rbrtj
[Cases][AttachmentV2] Remove actions in open api docs (elastic#265141)
5aae148 
## Summary

Reverts `Actions` related docs because it will be deprecated post
attachment V2 migrations.


### Checklist

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
SoniaSanzV pushed a commit to SoniaSanzV/kibana that referenced this pull request Apr 27, 2026
@christineweng @kibanamachine @SoniaSanzV
[Cases][AttachmentV2] Remove actions in open api docs (elastic#265141)
b5101c9 
## Summary

Reverts `Actions` related docs because it will be deprecated post
attachment V2 migrations.


### Checklist

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@janmonschke janmonschke janmonschke approved these changes

@nastasha-solomon nastasha-solomon nastasha-solomon approved these changes

Assignees

@christineweng christineweng

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes Team:Cases Security Solution Cases team v9.4.0 v9.5.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@christineweng @elasticmachine @kibanamachine @janmonschke @nastasha-solomon