Windows installer now ensures that legacy osquery installations gets removed during clean install - #9048
Conversation
…removed during clean install
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9048 +/- ##
========================================
Coverage 60.24% 60.25%
========================================
Files 472 473 +1
Lines 45759 46063 +304
========================================
+ Hits 27566 27753 +187
- Misses 15623 15706 +83
- Partials 2570 2604 +34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| } | ||
|
|
||
| if err := ioutil.WriteFile(path, contents.Bytes(), constant.DefaultFileMode); err != nil { | ||
| return fmt.Errorf("epowershell installer utils file write: %w", err) |
There was a problem hiding this comment.
Thanks, just fixed this
| @@ -0,0 +1 @@ | |||
| * Windows installer now ensures that installed osquery versio get removed before installing Orbit | |||
zwass
left a comment
There was a problem hiding this comment.
I'll give the code a more thorough review (only skimmed it so far). Can you please document in the PR description what manual QA steps you went through? For these kinds of complex agent PRs it's really helpful for me to get confidence that we've gone through a thorough set of tests.
Hey @zwass, sure, that's a good point! I've manually tested the following scenarios. The scenarios3 and scenario4 are the ones that caused issues on the field Scenario 1 - Clean Orbit installation
Scenario 2 - Clean Orbit uninstallation
Scenario 3 - Problematic Scenario - Multiple logged-in users with legacy osquery installation
Scenario 4 - Problematic Scenario - Multiple users with legacy osquery installation - Only one user is logged in
|
…oving installer_utils.ps1 deployment by removing duplicate
zwass
left a comment
There was a problem hiding this comment.
@marcosd4h besides the logging, this lgtm. If there's a reason for not doing the logging I'm good to merge as-is.
Let's try to merge this today (mergefreeze can be skipped due to bugfix).
| } | ||
| catch | ||
| { | ||
|
|
There was a problem hiding this comment.
Can/should we be logging in this and other catch blocks?
There was a problem hiding this comment.
@zwass Yes, this is a good point. Console logs are captured and logged by msiexec, so adding log lines here is a good idea. I've just pushed the change to add support for this.
|
@xpkoala This PR adds support for |
This relates to #8891
This PR introduces Wix custom actions usage
Checklist for submitter
If some of the following don't apply, delete the relevant line.
changes/ororbit/changes/.