-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Set default schedule to "paused" for any Job in Test Env #75
Comments
We also need to probably need to hard set the schedule as None if the env is local. |
For local: we will default it to None, but will give an option to override and schedule it |
for local -- instead of setting schedule to None, we should make the workflow status PAUSE. There are time, when team wants test Quartz expressions. PAUSED is better than override flag. |
I agree, makes sense! |
Is your feature request related to a problem? Please describe.
In order to minimize cost, any deployed job that is running on a schedule should have a state set as paused in the test environment.
Cloud Information
Describe the solution you'd like
Any deployment of a Job/pipelines in brickflow should be set as "paused" if specified to be running on a schedule when deployed to any non prod environment.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: