[8.x](backport #6498) Add ability to enroll with defined ID and replace_token #6806
Conversation
This file contains 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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Allows an Elastic Agent to enroll with a defined ID and replacement token to allow it to replace an existing Elastic Agent. The original Elastic Agent must have also been enrolled with the same --replace-token or it will not be allow to enroll if the --id collides with an existing Elastic Agent. (cherry picked from commit 8a878fc)
mergify
bot
requested review from
swiatekm and
pchila
and removed request for
a team
github-actions
bot
added
enhancement
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
swiatekm
approved these changes
Feb 11, 2025
|
buildkite test this |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Adds new
--id(ELASTIC_AGENT_IDenv for container) and--replace-token(FLEET_REPLACE_TOKENenv for container) to enrollment.Why is it important?
Allows an Elastic Agent to enroll with a defined ID and replacement token to allow it to replace an existing Elastic Agent. The original Elastic Agent must have also been enrolled with the same
--replace-tokenor it will not be allow to enroll if the--idcollides with an existing Elastic Agent.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files(no config changes)[ ] I have added tests that prove my fix is effective or that my feature works(cannot unit test)./changelog/fragmentsusing the changelog toolDisruptive User Impact
None
How to test this PR locally
You need this PR (elastic/fleet-server#4290) from Fleet Server and have that Fleet Server running to enroll. Then you can build this PR and run enroll with
--idand--replace-token.Related issues
This is an automatic backport of pull request #6498 done by [Mergify](https://mergify.com).