-
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] Support package capabilities filtering #162435
[Fleet] Support package capabilities filtering #162435
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
e46e2c2
to
7c64029
Compare
…-ref HEAD~1..HEAD --fix'
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
Is this pr closing #161215 ? |
….com:nchaulet/kibana into feature-fleet-support-capabilities-filtering
Yes it is
Yes I just added a commit with the |
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
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @nchaulet |
Summary
Depends on elastic/package-registry#1061
Pass the capabilities configured in
xpack.fleet.internal.capabilities
to the package registry to allow filtering on capabilities.Manual test instructions
elastic.capabilities
to a package andxpack.fleet.internal.capabilities
to you kibana.dev.yml file to see that filitering is correctly done.Todo
Closes #161215