Skip to content

Can we remove workflow code from PowerShell Core? #9570

@KirkMunro

Description

@KirkMunro

ActionPreference.Suspend is not supported in PowerShell Core (it's only used for workflows, which are not in PowerShell Core). Today it just adds confusion to the code with checks to ensure that value isn't used where there doesn't need to be any. The checks should also be performed by a PSSA rule rather than in source code (similar to ActionPreference.Ignore, as was decided in #4348). Do we need to keep ActionPreference.Suspend checks around at this point or can we just remove the half-dozen checks related to it from the source code?

Further, if we remove these checks (for the same reason we removed the checks for ActionPreference.Ignore), do we need the ActionPreference.Suspend enumeration value kept around at all?

@SteveL-MSFT: For committee review.

[Update]
As per the committee review, all workflow code should be removed. Here is the list of items requiring removal:

  • workflow keyword
  • parallel keyword (used for parallel activities in workflow)
  • sequence keyword (used for sequential activities in workflow)
  • inlinescript activity block (used for activities outside of workflow)
  • -parallel parameter on foreach statement
  • Checkpoint-Workflow activity (command)
  • Suspend-Workflow activity (command)
  • ActionPreference.Suspend enumeration
  • plus all related classes/methods

Metadata

Metadata

Assignees

No one assigned

    Labels

    Committee-ReviewedPS-Committee has reviewed this and made a decisionIssue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-FixedThe issue is fixed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions