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

move .search-acl-filter-* permissions to the right api key creation function #160457

Merged
merged 1 commit into from
Jun 23, 2023

Conversation

seanstory
Copy link
Member

@seanstory seanstory commented Jun 23, 2023

Summary

I'd added this logic in #159840 and turns out that was the wrong place to influence connector api keys.

Checklist

For maintainers

@seanstory seanstory added release_note:skip Skip the PR/issue when compiling release notes v8.9.0 v8.10.0 labels Jun 23, 2023
@seanstory seanstory requested a review from a team June 23, 2023 20:28
@seanstory seanstory enabled auto-merge (squash) June 23, 2023 20:51
@seanstory seanstory merged commit 8251481 into main Jun 23, 2023
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id before after diff
enterpriseSearch 14 16 +2
securitySolution 416 420 +4
total +6

Total ESLint disabled count

id before after diff
enterpriseSearch 15 17 +2
securitySolution 497 501 +4
total +6

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

@seanstory seanstory deleted the seanstory/fix-acl-filter-api-key-location branch June 23, 2023 21:35
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jun 23, 2023
…unction (elastic#160457)

## Summary
I'd added this logic in elastic#159840
and turns out that was the wrong place to influence connector api keys.

### Checklist

- [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

### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

(cherry picked from commit 8251481)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.9

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 Jun 23, 2023
…tion function (#160457) (#160465)

# Backport

This will backport the following commits from `main` to `8.9`:
- [move .search-acl-filter-* permissions to the right api key creation
function (#160457)](#160457)

<!--- Backport version: 8.9.7 -->

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

<!--BACKPORT [{"author":{"name":"Sean
Story","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-06-23T21:35:26Z","message":"move
.search-acl-filter-* permissions to the right api key creation function
(#160457)\n\n## Summary\r\nI'd added this logic in
https://github.com/elastic/kibana/pull/159840\r\nand turns out that was
the wrong place to influence connector api keys.\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8251481340c8125e450ef1386cbd73209de882ff","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.9.0","v8.10.0"],"number":160457,"url":"https://github.com/elastic/kibana/pull/160457","mergeCommit":{"message":"move
.search-acl-filter-* permissions to the right api key creation function
(#160457)\n\n## Summary\r\nI'd added this logic in
https://github.com/elastic/kibana/pull/159840\r\nand turns out that was
the wrong place to influence connector api keys.\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8251481340c8125e450ef1386cbd73209de882ff"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/160457","number":160457,"mergeCommit":{"message":"move
.search-acl-filter-* permissions to the right api key creation function
(#160457)\n\n## Summary\r\nI'd added this logic in
https://github.com/elastic/kibana/pull/159840\r\nand turns out that was
the wrong place to influence connector api keys.\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8251481340c8125e450ef1386cbd73209de882ff"}}]}]
BACKPORT-->

Co-authored-by: Sean Story <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team:EnterpriseSearch v8.9.0 v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants