powershell/PSMissingModuleManifestField

powershell/PSMissingModuleManifestField 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 because Dockerfiles do not ship PowerShell module manifests (.psd1 files) — this rule targets module-authoring artifacts that are out of scope for container builds. Re-enable it with include = ["powershell/PSMissingModuleManifestField"] or by setting rules.powershell.PSMissingModuleManifestField.severity = "warning" in .tally.toml.

Description

A module manifest is a .psd1 file that contains a hash table. The keys and values in the hash table describe the contents and attributes of the module, define the prerequisites, and determine how the components are processed. Module manifests must contain the following keys (and a corresponding value) to be considered valid:

ModuleVersion

All other keys are optional. The order of the entries is not important.

How

Please consider adding the missing fields to the manifest.

Examples

Problematic code

@{
    Author              = 'PowerShell Author'
    NestedModules       = @('.\mymodule.psm1')
    FunctionsToExport   = '*'
    CmdletsToExport     = '*'
    VariablesToExport   = '*'
}

Correct code

@{
    ModuleVersion       = '1.0'
    Author              = 'PowerShell Author'
    NestedModules       = @('.\mymodule.psm1')
    FunctionsToExport   = '*'
    CmdletsToExport     = '*'
    VariablesToExport   = '*'
}

Source

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

powershell/PSMisleadingBacktick

powershell/PSPlaceCloseBrace

⌘I

​Description

​How

​Examples

​Problematic code

​Correct code

​Source

Description

How

Examples

Problematic code

Correct code

Source