-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Use elastic_agent package to build monitoring permissions for elastic agent #112730
[Fleet] Use elastic_agent package to build monitoring permissions for elastic agent #112730
Conversation
…lastic-agent-package-permissions
55b67e4
to
77e7c2d
Compare
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Public APIs missing comments
Page load bundle
History
To update your PR or re-run it, just comment with: cc @nchaulet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 - things seem well thought out in how we fall back to our previous hard coded permissions in case we can't resolve permissions from the package.
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Description
Resolve #107738
Currently we hardcode the permissions we gave to the agent for monitoring, that PR use the data streams defined by the elastic_agent package to build the permissions instead.
Implementations details
If the
elastic_agent
package is not installed we still return an hardcoded version of the permissions (similar of what we are currently returning for permissions)Tests