[UII] Make output and fleet server non-editable for agentless policies#218905
Merged
jen-huang merged 8 commits intoelastic:mainfrom Apr 24, 2025
Merged
[UII] Make output and fleet server non-editable for agentless policies#218905jen-huang merged 8 commits intoelastic:mainfrom
jen-huang merged 8 commits intoelastic:mainfrom
Conversation
…hen creating agentless policies. Correct them on Fleet setup if necessary
jen-huang
added
release_note:fix
backport:skip
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
jen-huang
added
ci:cloud-deploy
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
cc @jen-huang |
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
elastic#218905) ## Summary Resolves https://github.com/elastic/security-team/issues/10971. This PR makes it so that on Cloud, agentless policies cannot move off of the default managed Fleet Server host and ES output. This is done by: - Explicitly writing `fleet_server_host_id` and `data_output_id` fields to the agentless policy that is created when adding an agentless integration - On ECH, these are `fleet-default-fleet-server-host` and `fleet-default-output` respectively - On Serverless, these are `default-fleet-server` and `es-default-output` - During Fleet setup, agentless policies without these fields set up correctly will be backfilled to the correct values ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Resolves https://github.com/elastic/ingest-dev/issues/5459.
This PR makes it so that on Cloud, agentless policies cannot move off of the default managed Fleet Server host and ES output. This is done by:
fleet_server_host_idanddata_output_idfields to the agentless policy that is created when adding an agentless integrationfleet-default-fleet-server-hostandfleet-default-outputrespectivelydefault-fleet-serverandes-default-outputChecklist
release_note:*label is applied per the guidelines