API Reference
Cmdlet
New-ConfigurationModuleSkip
Provides a way to ignore certain commands or modules during build process and continue module building on errors.
Remarks
Useful for optional dependencies where you want builds to succeed even if a tool module is not available (e.g. optional analyzers, formatters, helpers).
Examples
Ignore an optional module and continue on missing dependency
PS>
New-ConfigurationModuleSkip -IgnoreModuleName 'PSScriptAnalyzer' -Force
Prevents build failure when the module is not installed in the environment.
Ignore specific functions for cross-platform builds
PS>
New-ConfigurationModuleSkip -IgnoreModuleName 'Microsoft.PowerShell.Security' -IgnoreFunctionName 'Get-AuthenticodeSignature','Set-AuthenticodeSignature' -Force
Common Parameters
This command supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
For more information, see about_CommonParameters.
Syntax
New-ConfigurationModuleSkip [-FailOnMissingCommands] [-Force] [-IgnoreFunctionName <String[]>] [-IgnoreModuleName <String[]>] [<CommonParameters>]Parameter set:
All Parameter SetsParameters
- FailOnMissingCommands SwitchParameter
- Fail build when unresolved commands are detected during merge.
- Force SwitchParameter
- Force build process to continue even if the module or command is not available.
- IgnoreFunctionName String[]
- Ignore function name(s). If the function is not available it will be ignored.
- IgnoreModuleName String[]
- Ignore module name(s). If the module is not available it will be ignored.
Outputs
System.Object