powershell/PSUseProcessBlockForPipelineCommand

powershell/PSUseProcessBlockForPipelineCommand is a PSScriptAnalyzer diagnostic emitted by tally for PowerShell snippets embedded in Dockerfiles.

Property	Value
Severity	Warning
Category	PSScriptAnalyzer
Default	Disabled in tally
Auto-fix	No

tally disables this rule by default for Dockerfile RUN snippets because a RUN executes statements inline rather than defining cmdlets, parameters, or modules with external callers. Re-enable it with include = ["powershell/PSUseProcessBlockForPipelineCommand"] or by setting rules.powershell.PSUseProcessBlockForPipelineCommand.severity = "warning" in .tally.toml.

Description

Functions that support pipeline input should always handle parameter input in a process block. Unexpected behavior can result if input is handled directly in the body of a function where parameters declare pipeline support.

Examples

Problematic code

Function Get-Number
{
    [CmdletBinding()]
    Param(
        [Parameter(ValueFromPipeline)]
        [int]
        $Number
    )

    $Number
}

Result

PS C:\> 1..5 | Get-Number
5

Correct code

Function Get-Number
{
    [CmdletBinding()]
    Param(
        [Parameter(ValueFromPipeline)]
        [int]
        $Number
    )

    process
    {
        $Number
    }
}

Result

PS C:\> 1..5 | Get-Number
1
2
3
4
5

Source

This rule documentation is adapted from Microsoft’s PSScriptAnalyzer documentation for UseProcessBlockForPipelineCommand, licensed under CC BY 4.0.

powershell/PSUsePSCredentialType

powershell/PSUseShouldProcessForStateChangingFunctions

⌘I

​Description

​Examples

​Problematic code

​Result

​Correct code

​Result

​Source

Description

Examples

Problematic code

Result

Correct code

Result

Source