[Elastic Agent] Handle migration of agent_info to agent in Fleet configuration#19488
Closed
blakerouse wants to merge 2 commits intoelastic:masterfrom
Closed
[Elastic Agent] Handle migration of agent_info to agent in Fleet configuration#19488blakerouse wants to merge 2 commits intoelastic:masterfrom
blakerouse wants to merge 2 commits intoelastic:masterfrom
Conversation
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
4 tasks
Contributor
Author
|
Closing, going to just mark it breaking for 7.8 -> 7.9. |
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
3 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.
What does this PR do?
#19248 changed the Fleet config to use
agent.idinstead ofagent_info.ID. This was so the configuration could match what Endpoint was expecting.This PR handles upgrading this transparently on startup for Elastic Agent, so the agent ID will not be re-generated when upgrading to a build that includes #19243
Why is it important?
So the Agent ID is not regenerated when starting Agent after upgrading.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.