fix(5595): added logic to use development binary path for uninstall #5877
+23
−3
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?
Updates how the
upgrade
command works when used with the--force
and--develop
flags. Currently if a development agent is already installed, and if a user wants to force install a new development agent, the command uninstalls the production agent, if it exists, and tries to install the development agent again.Checklist
./changelog/fragments
using the changelog toolHow to test this PR locally
--force
flag and confirm that at the end of the operation bothelastic-agent
andelastic-development-agent
binaries are installed and that both agents are healthyRelated issues
--force
ignores--develop
and uninstalls production agent instead #5595