-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"install -f" uses exec to uninstall an existing agent #4965
Merged
ycombinator
merged 18 commits into
elastic:main
from
michel-laterman:tamper-cheeck-unintall
Jun 28, 2024
+184
−95
Merged
Changes from 7 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
2332b43
Add explicit check for token and tamper protection in Uninstall func
michel-laterman b27ce20
fix typo
michel-laterman 38784de
Merge branch 'main' into tamper-cheeck-unintall
jlind23 bcceff5
Load features from config, fix protection flag load
michel-laterman ed57cf0
Merge remote-tracking branch 'origin/main' into tamper-cheeck-unintall
michel-laterman 37d51d6
Merge branch 'main' into tamper-cheeck-unintall
michel-laterman f0b7d88
Change approach to execute elastic-agent uninstall command
michel-laterman b210ac2
Add e2e test
michel-laterman 71ba9e7
lookup agent binary on path, fix test
michel-laterman 2a527d5
fix test
michel-laterman dc66162
Add flag that preserves old approach
michel-laterman 26dae28
Merge branch 'main' into tamper-cheeck-unintall
michel-laterman a700b50
fix typo
michel-laterman 3048715
change args format in test
michel-laterman 5ffd08a
Use same fixture
michel-laterman 848da37
Hide new option
michel-laterman 39b5220
Merge branch 'main' into tamper-cheeck-unintall
michel-laterman bfd819e
Merge branch 'main' into tamper-cheeck-unintall
michel-laterman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
35 changes: 35 additions & 0 deletions
35
changelog/fragments/1718833116-Check-for-tamper-protection-when-uninstalling.yaml
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Kind can be one of: | ||
# - breaking-change: a change to previously-documented behavior | ||
# - deprecation: functionality that is being removed in a later release | ||
# - bug-fix: fixes a problem in a previous version | ||
# - enhancement: extends functionality but does not break or fix existing behavior | ||
# - feature: new functionality | ||
# - known-issue: problems that we are aware of in a given version | ||
# - security: impacts on the security of a product or a user’s deployment. | ||
# - upgrade: important information for someone upgrading from a prior version | ||
# - other: does not fit into any of the other categories | ||
kind: bug | ||
|
||
# Change summary; a 80ish characters long description of the change. | ||
summary: Check for tamper protection when install --force is used | ||
|
||
# Long description; in case the summary is not enough to describe the change | ||
# this field accommodate a description without length limits. | ||
# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. | ||
description: | | ||
When using "elastic-agent install -f", the agent will exec "elastic-agent uninstall -f" | ||
so that all path references are correctly loaded and tamper protection errors will cause | ||
the install attempt to fail. | ||
|
||
# Affected component; a word indicating the component this changeset affects. | ||
component: | ||
|
||
# PR URL; optional; the PR number that added the changeset. | ||
# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. | ||
# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. | ||
# Please provide it if you are adding a fragment for a different PR. | ||
#pr: https://github.com/owner/repo/1234 | ||
|
||
# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). | ||
# If not present is automatically filled by the tooling with the issue linked to the PR number. | ||
issue: https://github.com/elastic/elastic-agent/issues/4506 |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously this call to uninstall was failing because
paths.Components()
would use a value that reflected the location from whereelastic-agent install -f
was being ran and not the installed agent.This would result in the uninstall detecting 0 components, and skipping calling uninstall on each of the services, so endpoint uninstall was never called