[Core feature] Support for Pausing launchplans/Pipelines (Similar to Pausing DAGs in Airflow)

[avasani]

Motivation: Why do you think this is important?

Flyte currently lacks the ability to pause launchplan or pipelines, which is a common feature in other workflow orchestration tools like Airflow. Users need a way to temporarily halt all new executions of a workflow without deregistering or deleting it, especially during incidents or while deploying critical fixes.

All the pending execution request should go in wait queue if user triggers the remote-launchplan. If request could be executed if trigged as remote-workflow

Goal: What should the final outcome look like, ideally?

• A production workflow starts failing due to a bad deployment or unforeseen data issues.
• The user wants to prevent any new executions from starting while investigating and fixing the problem.
• In Airflow, this is achieved by pausing the DAG.

Describe alternatives you've considered

Missing feature in Flyte.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[kumare3]

@avasani Flyte supports recover mode. Even if things fail you can simply recover right? Why not do it this way instead of manual pausing.

One simple way of pausing is - just go and kill the flytepropeller pod and all progress will stop and when you restart it, it will just simply resume