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

[ResponseOps][Actions] Manual migration of action routes without access tags #204030

Merged
merged 3 commits into from
Dec 13, 2024

Conversation

adcoelho
Copy link
Contributor

@adcoelho adcoelho commented Dec 12, 2024

Connected with https://github.com/elastic/kibana-team/issues/1322

Summary

Since most action routes do not use access tags they need to be migrated to include a reason in the security params.

Documentation.

The following routes were migrated:

  • createConnectorRoute
  • deleteConnectorRoute
  • getConnectorRoute
  • getAllConnectorsRoute
  • updateConnectorRoute
  • listTypesRoute
  • executeConnectorRoute
  • getGlobalExecutionLogRoute
  • getGlobalExecutionKPIRoute
  • getAllConnectorsIncludingSystemRoute
  • listTypesWithSystemRoute
  • getOAuthAccessToken

@adcoelho adcoelho added release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v9.0.0 Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) labels Dec 12, 2024
@adcoelho adcoelho self-assigned this Dec 12, 2024
@adcoelho adcoelho requested a review from a team as a code owner December 12, 2024 14:07
@elasticmachine
Copy link
Contributor

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

Copy link
Member

@cnasikas cnasikas left a comment

Choose a reason for hiding this comment

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

The list_types and list_types_system do not perform any authorization. They do not use the actions client. Should we provide a different message for them?

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

cc @adcoelho

@adcoelho adcoelho merged commit 2dc790b into elastic:main Dec 13, 2024
8 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

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

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Dec 13, 2024
…ss tags (elastic#204030)

Connected with elastic/kibana-team#1322

## Summary

Since most action routes do not use access tags they need to be migrated
to include a reason in the security params.

[Documentation.](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#opting-out-of-authorization-for-specific-routes)

The following routes were migrated:
- `createConnectorRoute`
- `deleteConnectorRoute`
- `getConnectorRoute`
- `getAllConnectorsRoute`
- `updateConnectorRoute`
- `listTypesRoute`
- `executeConnectorRoute`
- `getGlobalExecutionLogRoute`
- `getGlobalExecutionKPIRoute`
- `getAllConnectorsIncludingSystemRoute`
- `listTypesWithSystemRoute`
- `getOAuthAccessToken`

(cherry picked from commit 2dc790b)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.x

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 13, 2024
…t access tags (#204030) (#204215)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ResponseOps][Actions] Manual migration of action routes without
access tags (#204030)](#204030)

<!--- 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-13T13:57:13Z","message":"[ResponseOps][Actions]
Manual migration of action routes without access tags
(#204030)\n\nConnected with
https://github.com/elastic/kibana-team/issues/1322\r\n\r\n##
Summary\r\n\r\nSince most action routes do not use access tags they need
to be migrated\r\nto include a reason in the security
params.\r\n\r\n\r\n[Documentation.](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#opting-out-of-authorization-for-specific-routes)\r\n\r\nThe
following routes were migrated:\r\n- `createConnectorRoute`\r\n-
`deleteConnectorRoute`\r\n- `getConnectorRoute`\r\n-
`getAllConnectorsRoute`\r\n- `updateConnectorRoute`\r\n-
`listTypesRoute`\r\n- `executeConnectorRoute`\r\n-
`getGlobalExecutionLogRoute`\r\n- `getGlobalExecutionKPIRoute`\r\n-
`getAllConnectorsIncludingSystemRoute`\r\n-
`listTypesWithSystemRoute`\r\n-
`getOAuthAccessToken`","sha":"2dc790bbc024fd805aaafc9b2f6a5cc79dd2c6e2","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:Alerting/RuleActions","backport:prev-minor","v8.18.0"],"title":"[ResponseOps][Actions]
Manual migration of action routes without access tags
","number":204030,"url":"https://github.com/elastic/kibana/pull/204030","mergeCommit":{"message":"[ResponseOps][Actions]
Manual migration of action routes without access tags
(#204030)\n\nConnected with
https://github.com/elastic/kibana-team/issues/1322\r\n\r\n##
Summary\r\n\r\nSince most action routes do not use access tags they need
to be migrated\r\nto include a reason in the security
params.\r\n\r\n\r\n[Documentation.](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#opting-out-of-authorization-for-specific-routes)\r\n\r\nThe
following routes were migrated:\r\n- `createConnectorRoute`\r\n-
`deleteConnectorRoute`\r\n- `getConnectorRoute`\r\n-
`getAllConnectorsRoute`\r\n- `updateConnectorRoute`\r\n-
`listTypesRoute`\r\n- `executeConnectorRoute`\r\n-
`getGlobalExecutionLogRoute`\r\n- `getGlobalExecutionKPIRoute`\r\n-
`getAllConnectorsIncludingSystemRoute`\r\n-
`listTypesWithSystemRoute`\r\n-
`getOAuthAccessToken`","sha":"2dc790bbc024fd805aaafc9b2f6a5cc79dd2c6e2"}},"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/204030","number":204030,"mergeCommit":{"message":"[ResponseOps][Actions]
Manual migration of action routes without access tags
(#204030)\n\nConnected with
https://github.com/elastic/kibana-team/issues/1322\r\n\r\n##
Summary\r\n\r\nSince most action routes do not use access tags they need
to be migrated\r\nto include a reason in the security
params.\r\n\r\n\r\n[Documentation.](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization#opting-out-of-authorization-for-specific-routes)\r\n\r\nThe
following routes were migrated:\r\n- `createConnectorRoute`\r\n-
`deleteConnectorRoute`\r\n- `getConnectorRoute`\r\n-
`getAllConnectorsRoute`\r\n- `updateConnectorRoute`\r\n-
`listTypesRoute`\r\n- `executeConnectorRoute`\r\n-
`getGlobalExecutionLogRoute`\r\n- `getGlobalExecutionKPIRoute`\r\n-
`getAllConnectorsIncludingSystemRoute`\r\n-
`listTypesWithSystemRoute`\r\n-
`getOAuthAccessToken`","sha":"2dc790bbc024fd805aaafc9b2f6a5cc79dd2c6e2"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Antonio <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants