Coupled with the fact that the error message mentions it can't find any .PSDeploy.ps1 files in the given location, the -Filter is applied as *undeployed.ps1, which can break the ability to do deployments unexpectedly, with very little information as to what's actually going wrong.
Given that you're only searching a single directory (I think?) It is probably fine to instead use a Where-Object filter or an -Include filter instead (not sure if those are case sensitive on Unix systems, but I would suspect not, given they're done by the cmdlets and not the filesystem itself?)
Coupled with the fact that the error message mentions it can't find any
.PSDeploy.ps1files in the given location, the -Filter is applied as*undeployed.ps1, which can break the ability to do deployments unexpectedly, with very little information as to what's actually going wrong.Given that you're only searching a single directory (I think?) It is probably fine to instead use a Where-Object filter or an -Include filter instead (not sure if those are case sensitive on Unix systems, but I would suspect not, given they're done by the cmdlets and not the filesystem itself?)