Skip to content

New/Set-CcmDeploymentStep should have parameters for -AllowPrerelease and -Version for basic steps #71

@vexx32

Description

@vexx32

Is Your Feature Request Related To A Problem? Please describe.

CCM v0.10.0 added functionality for Basic deployment steps to include additional parameters, namely --pre and --version. The *-CCMDeploymentStep commands do not currently have functionality for these parameters.

Describe The Solution. Why is it needed?

Add extra parameters to the Basic parameter set for these commands and ensure they are passed into the API correctly.

API expects the additional parameters to be provided as part of the script value in the JSON input, so the format is now $ChocoCommand|$PackageName|$Version|$AllowPrerelease (although I believe omitting the latter two portions entirely is acceptable for backwards compat reasons if neither needs to be provided?)

Related Issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    0 - BacklogIssue is accepted, but is not ready to be worked on or not in current sprint.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