Fix xpack info and usage reports for operator privileges #65867
Merged
Conversation
This file contains hidden or 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
ywangd
added
>non-issue
:Security/Security
|
Pinging @elastic/es-security (Team:Security) |
|
@elasticmachine update branch |
I assume you will make sure they know that. |
Good point. I will initiate an email for it. |
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.
This is a follow-up PR for #65256 to fix the xpack info and usage reports for operator privilegs. In summary, this PR ensures:
_xpackdoes not report operator privileges because it is categorised under security_xpack/usagereports operator privileges status under the security section_license/feature_usagereports last used time of operator privileges. It is up to the downstream to filter out this report if necessary.I tag this PR as
non-issuebecause the original changes are not released yet. Also this will not be backported separately because it will be backported along with the main changes (#65256).