[Rules migration] Use user profile UID instead of username #206299
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
e40pud
added
release_note:skip
|
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
semd
reviewed
Jan 10, 2025
...curity_solution/server/lib/siem_migrations/rules/data/rule_migrations_data_lookups_client.ts
Outdated
Show resolved
Hide resolved
💚 Build Succeeded
Metrics [docs]
History
cc @e40pud |
|
Starting backport for target branches: 8.x |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 12, 2025
…06299) ## Summary [Internal link](elastic/security-team#10820) to the feature details With these changes we switch to using user's `profile_id` instead of `username` as a user identification for the migration rules create and update operations. (cherry picked from commit a1f8532)
💚 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
Jan 12, 2025
…6299) (#206378) # Backport This will backport the following commits from `main` to `8.x`: - [[Rules migration] Use user profile UID instead of username (#206299)](#206299) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-12T12:06:13Z","message":"[Rules migration] Use user profile UID instead of username (#206299)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nWith these changes we switch to using user's `profile_id` instead of\r\n`username` as a user identification for the migration rules create and\r\nupdate operations.","sha":"a1f85326e8166857f51e581ae6a3e94bc480428e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:prev-minor"],"title":"[Rules migration] Use user profile UID instead of username","number":206299,"url":"https://github.com/elastic/kibana/pull/206299","mergeCommit":{"message":"[Rules migration] Use user profile UID instead of username (#206299)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nWith these changes we switch to using user's `profile_id` instead of\r\n`username` as a user identification for the migration rules create and\r\nupdate operations.","sha":"a1f85326e8166857f51e581ae6a3e94bc480428e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206299","number":206299,"mergeCommit":{"message":"[Rules migration] Use user profile UID instead of username (#206299)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nWith these changes we switch to using user's `profile_id` instead of\r\n`username` as a user identification for the migration rules create and\r\nupdate operations.","sha":"a1f85326e8166857f51e581ae6a3e94bc480428e"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <[email protected]>
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Jan 13, 2025
…06299) ## Summary [Internal link](elastic/security-team#10820) to the feature details With these changes we switch to using user's `profile_id` instead of `username` as a user identification for the migration rules create and update operations.
viduni94
pushed a commit
to viduni94/kibana
that referenced
this pull request
Jan 23, 2025
…06299) ## Summary [Internal link](elastic/security-team#10820) to the feature details With these changes we switch to using user's `profile_id` instead of `username` as a user identification for the migration rules create and update operations.
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.
Summary
Internal link to the feature details
With these changes we switch to using user's
profile_idinstead ofusernameas a user identification for the migration rules create and update operations.