Skip to content
This repository was archived by the owner on Apr 28, 2018. It is now read-only.
This repository was archived by the owner on Apr 28, 2018. It is now read-only.

ShouldContinue & ShouldProcess attribute missing in the Cmdlets #171

Open
@DexterPOSH

Description

@DexterPOSH

Output of $PSVersionTable (from a powershell process):

Name                           Value
----                           -----
PSVersion                      5.1.14393.576
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.576
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Output of ipmo Docker; (module Docker).Version.ToString() (from a powershell process):

0.1.0.111

Steps to reproduce the issue:

  1. Get-Command -Module Docker -ParameterName WhatIf
  2. Get-Command -Module Docker -ParameterName Force ; Get-Command -Module Docker -ParameterName Confirm

What actually happened?:

Throws an error that no matching commands include a parameter named 'whatif' or 'confirm'

What did you expect to happen?:
As a best practice while developing cmdlets for PowerShell, it is recommended to Support ShouldProcess & ConfirmImpact cmdlet attributes.

Additional information:
Creating a Cmdlet that Modifies the System

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions