Description

In the Workflow.post_init method, we now enforce that if the environment (as determined by BRICKFLOW_ENV is one of ["local", "dev", "test"] and the workflow’s [schedule_pause_status] is "UNPAUSED", it is automatically set to "PAUSED". This prevents non‑production workflows from running unintentionally.

Related Issue

#75

Motivation and Context

In non-production environments, workflows were unintentionally being executed with an “UNPAUSED” schedule status by default. This behavior posed risks during development and testing by potentially triggering workflows when it wasn’t intended. To address this, we updated the logic so that workflows running in environments such as local, dev, or test automatically have their schedule status set to "PAUSED" even if not explicitly configured. This ensures that workflows in non-production settings remain inactive until deliberately re-enabled.

Additionally, test cases related to bundle generation were enhanced. For non-local environments, required Git configuration (including a valid reference) is now provided, which prevents validation errors during bundle creation. These improvements help safeguard unintended workflow executions and ensure the bundle generation process accurately reflects the intended scheduling behavior across various environments.

How Has This Been Tested?

Unit Testing

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.