Skip to content

New-CCMDeploymentStep -Type parameter feels redundant #37

@vexx32

Description

@vexx32
$step = @{
    Deployment   = $Deployment.Name
    Name         = 'Choco Upgrade All'
    TargetGroup  = $Group.Name 
    # why is this here?
    Type         = 'Basic' 
    ChocoCommand = 'upgrade' 
    PackageName  = 'all'
}
New-CCMDeploymentStep @step

I think the best way forward here is to remove the Type parameter completely (it's not really adding anything here) and just have the -Script or -ChocoCommand (and -PackageName) parameters be mandatory in their sets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementIssues that introduce new functionality to the project, or enhances/updates existing functionality.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions