Skip to content

Add -Force parameter on any ConfirmImpact="High" cmdlets #218

Closed
@TylerLeonhardt

Description

@TylerLeonhardt

Feature Idea Summary

We should have a -Force to skip over confirmation since -Confirm:$false is tedious.

Feature Idea Additional Details

Take a look at @KevinMarquette's awesome blog post on implementing whatif/confirm/force:
https://powershellexplained.com/2020-03-15-Powershell-shouldprocess-whatif-confirm-shouldcontinue-everything/#implementing--force

Requested Assignment

I'm just suggesting this idea at this time.

Activity

added
enhancementAn issue or pull request introducing new functionality to the project.
triage neededAn issue that needs to be reviewed by a member of the team.
on Jun 2, 2020
added
discussionWe are looking for additional community feedback on this topic before proceeding further.
good first issueIf you're new to the project (or to OSS in general) and you'd like to contribute, try this one.
help wantedAnyone in the community is welcome to do this work
up for grabsAnyone in the community is welcome to do this work
and removed
triage neededAn issue that needs to be reviewed by a member of the team.
on Jun 2, 2020
HowardWolosky

HowardWolosky commented on Jun 2, 2020

@HowardWolosky
Contributor

I had brought this up initially when the idea was being introduced in #145. I think that doing this makes sense, as -Force was my natural instinct for how to avoid the prompting before learning about -Confirm:$false (which is why I've been enforcing having a -Confirm:$false example with every command that is ConfirmImpact='High'.

I like that by having both, there's the "standard" way that has built-in support by PowerShell, but also the more "natural" way that people might be inclined to initially try.

This wouldn't be a breaking change, so this seems reasonable for someone to tackle right away if they're interested.

giuseppecampanelli

giuseppecampanelli commented on Jun 3, 2020

@giuseppecampanelli
Contributor

I'll tackle this 😄

HowardWolosky

HowardWolosky commented on Jun 3, 2020

@HowardWolosky
Contributor

@themilanfan - it's yours. Thanks so much!

added
in progressWork on this issue is already underway. Please don't work start new work on it.
and removed
good first issueIf you're new to the project (or to OSS in general) and you'd like to contribute, try this one.
help wantedAnyone in the community is welcome to do this work
up for grabsAnyone in the community is welcome to do this work
on Jun 3, 2020
added a commit that references this issue on Jun 10, 2020
3c642d2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionWe are looking for additional community feedback on this topic before proceeding further.enhancementAn issue or pull request introducing new functionality to the project.in progressWork on this issue is already underway. Please don't work start new work on it.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @TylerLeonhardt@giuseppecampanelli@HowardWolosky

      Issue actions

        Add `-Force` parameter on any `ConfirmImpact="High"` cmdlets · Issue #218 · microsoft/PowerShellForGitHub