[ResponseOps][Cases] Migrate cases APIs with access tags. #203746
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adcoelho
added
release_note:skip
|
Pinging @elastic/response-ops-cases (Feature:Cases) |
adcoelho
added
Team:ResponseOps
cnasikas
approved these changes
Dec 11, 2024
|
Starting backport for target branches: 8.x |
💚 Build Succeeded
Metrics [docs]
cc @adcoelho |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 11, 2024
…3746) ## Summary This PR migrates the cases routes that use `access:` tags according to the [documented guidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes). (cherry picked from commit 106bb15)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 11, 2024
) (#203781) # Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Cases] Migrate cases APIs with access tags. (#203746)](#203746) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-11T12:16:10Z","message":"[ResponseOps][Cases] Migrate cases APIs with access tags. (#203746)\n\n## Summary\r\n\r\nThis PR migrates the cases routes that use `access:` tags according to\r\nthe [documented\r\nguidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes).","sha":"106bb156fa46747bd8f46d417ebe4d5e10e23a36","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-minor","v8.18.0"],"title":"[ResponseOps][Cases] Migrate cases APIs with access tags.","number":203746,"url":"https://github.com/elastic/kibana/pull/203746","mergeCommit":{"message":"[ResponseOps][Cases] Migrate cases APIs with access tags. (#203746)\n\n## Summary\r\n\r\nThis PR migrates the cases routes that use `access:` tags according to\r\nthe [documented\r\nguidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes).","sha":"106bb156fa46747bd8f46d417ebe4d5e10e23a36"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203746","number":203746,"mergeCommit":{"message":"[ResponseOps][Cases] Migrate cases APIs with access tags. (#203746)\n\n## Summary\r\n\r\nThis PR migrates the cases routes that use `access:` tags according to\r\nthe [documented\r\nguidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes).","sha":"106bb156fa46747bd8f46d417ebe4d5e10e23a36"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Antonio <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
…3746) ## Summary This PR migrates the cases routes that use `access:` tags according to the [documented guidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes).
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Jan 13, 2025
…3746) ## Summary This PR migrates the cases routes that use `access:` tags according to the [documented guidelines](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#configuring-authorization-on-routes).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #198398
Summary
Connected with https://github.com/elastic/kibana-team/issues/1321
This PR migrates the cases routes that use
access:tags according to the documented guidelines.