[ BUG ] Import-FalconConfig only creates Script for a single platform

[bk-cs]

Describe the bug
Import-FalconConfig is not properly comparing Script files across multiple platform values because it checks the target CID for platform values before comparison. If the target CID does not have any Script files, or they are limited to a single platform, the Script files in the import that don't match the available platform values won't be evaluated for creation or modification.

To Reproduce
Use Import-FalconConfig with a Script file for import, targeting a CID that has no Script files in it currently, or only Script files for a single operating system.

This behavior could manifest in other import types as well, but was reproducible for Script files.

Expected behavior
Each possible operating system should be checked for creation.

Environment

• PSFalcon: 2.2.8

[bk-cs]

A fix has been added for the next PSFalcon release. If you'd like to resolve it for your local module before release, you can replace public\psf-config.ps1 using the steps outlined below.

Import-Module -Name PSFalcon
$ModulePath = (Show-FalconModule).ModulePath
(Invoke-WebRequest -Uri https://raw.githubusercontent.com/CrowdStrike/psfalcon/378fde6d06aca2b06610ddfe1c31a6462237f620/public/psf-config.ps1 -UseBasicParsing).Content > (Join-Path (Join-Path $ModulePath public) psf-config.ps1)

Please ensure that you close and re-open PowerShell and re-import PSFalcon before testing.