-
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] Only expose minimum needed config to browser #129619
Conversation
Pinging @elastic/fleet (Team:Fleet) |
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.
Small nit, overall change LGTM
@@ -47,7 +47,9 @@ const DEFAULT_BUNDLED_PACKAGE_LOCATION = path.join(__dirname, '../target/bundled | |||
export const config: PluginConfigDescriptor = { | |||
exposeToBrowser: { | |||
epm: true, |
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.
could we remove this line too? we don't have any epm.* configs
💛 Build succeeded, but was flakyTest Failures
Metrics [docs]
To update your PR or re-run it, just comment with: |
(cherry picked from commit 5a06e8f)
(cherry picked from commit 5a06e8f)
(cherry picked from commit 5a06e8f)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 5a06e8f) Co-authored-by: Josh Dover <[email protected]>
(cherry picked from commit 5a06e8f) Co-authored-by: Josh Dover <[email protected]>
(cherry picked from commit 5a06e8f) Co-authored-by: Josh Dover <[email protected]>
Summary
This changes Fleet's config to only expose the
xpack.fleet.agents.enabled
flag instead of the entirexpack.fleet.agents.*
object to the browser. The other flags were unused.