[Agent] Windows spawning process fix #17751
Merged
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
|
Pinging @elastic/ingest-management (Project:fleet) |
ph
added
[zube]: In Review
needs_backport
michalpristas
added a commit
to michalpristas/beats
that referenced
this pull request
Apr 20, 2020
[Agent] Windows spawning process fix (elastic#17751) (cherry picked from commit 10de8be)
6 tasks
ph
pushed a commit
that referenced
this pull request
Apr 21, 2020
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?
When windows process is spawned its WD is set to agents WD. this fixes it so beat can pick up default config out of its directory
Why is it important?
Without this beat tries to lookup for default config e.g metricbeat.yml in an agents home dir. This config is not there so it fails.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.