[Fleet] Do not generate agent.protection and signed part full policy for standalone policies#217897
Merged
nchaulet merged 3 commits intoApr 14, 2025
Conversation
…for standalone policies
nchaulet
added
release_note:skip
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Member
Author
|
@elasticmachine merge upstream |
| } | ||
| if (options?.standalone) { | ||
| delete fullAgentPolicy.agent?.protection; | ||
| delete fullAgentPolicy.signed; |
Contributor
There was a problem hiding this comment.
nit: do we need this line if signed is not set in the previous conditional?
Member
Author
|
@elasticmachine merge upstream |
Contributor
💚 Build Succeeded
Metrics [docs]
History
cc @nchaulet |
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.
Description
Resolve #217895
We should not generate
agent.protectionandsignedpart of the full policy for standalone policies, that PR fix that.Tests
I added relevant unit tests.
Try to add a standalone agent and check the related properties are not present