CUT-4632: Fix CrowdStrike sensor download filter #651
Merged
+6
−7
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
kmaranionjc
previously approved these changes
Feb 18, 2025
kmaranionjc
previously approved these changes
Feb 18, 2025
jworkmanjc
previously approved these changes
Feb 18, 2025
jworkmanjc
approved these changes
Feb 18, 2025
kmaranionjc
approved these changes
Feb 18, 2025
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.
Issues
What does this solve?
CrowdStrike recently changed the default sort when pulling sensor download from release_date to platform causing issues when attempting to sort the latest installers only finding linux sensors.
Added a filter for the Windows platform on the sensors/combined/installers/v1 endpoint to alleviate the issue and no longer need to rely on grouping/sorting all results from the endpoint in PowerShell
Is there anything particularly tricky?
N/A
How should this be tested?
Pull the latest version of the script and validate that installs no longer result in an error