bk-cs
bk-cs
I was able to narrow down the error (which only occurs when using PowerShell Core) to the `Confirm-Parameter` private function. Through some testing, I believe I have an updated version...
Leaving open in case others run into this issue before the 2.2.3 release.
Resolved in v2.2.3 release.
Thanks for the report! This is expected behavior as the API itself requires a `status` whenever a `comment` is given. The module currently checks for the presence of the parameters...
Resolved in v2.2.3 release.
* Could you provide an example CSV? * Could you provide a transcript from running the commands? Please include `$VerbosePreference = 'Continue'` to ensure that the API calls are shown....
Sorry, attaching via email didn't work properly. Is there another method you could use to host the output? Thus far I've been unable to reproduce this issue. Until I figure...
Can you try the following? * Copy the contents of this file: https://raw.githubusercontent.com/CrowdStrike/psfalcon/2.2.1/Public/psf-output.ps1 * Replace your local copy of `Public\psf-output.ps1` with those contents * Restart PowerShell, re-import PSFalcon and re-test...
`Set-Property` is a function used by PSFalcon v2.2.0, but the error is coming from v2.1.9. It looks like you may have more than one version of PSFalcon on your system...
> Oh OK, I got your point. But if you remember – I ran into another issue with PSFalcon v2.2.0 where it seems to hit some limitations and the export...