[Request] Add auto-disable feature for DAGs in test or personal environments

[wimdehaes]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Make it possible for a (test/personal) environment to auto-disable all dags at the end of the day.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently when testing dags in my personal environment, I often forget to disable these DAGs when I am finished. This leads to costs that can easily be avoided. If there was some kind of way you could auto disable DAGs at the end of the day for a certain environment, we could avoid these costs. This could be done by marking the environment as test/personal or by adding an option to configure this auto-disable (maybe at DAG level)

Are you currently working around this issue?
Adding reminders in my calendar to disable the DAGs

[stijndehaes]

@wimdehaes cool idea!

I want to add another possibility, we could suspend the whole environment. The biggest downside of this is that when it's started again it would backfill all the dags that were not stopped.
So maybe a combination fo both could result in the biggest cost savings

[pdmuinck]

If you create dags without a schedule then your dag is kind of disabled by default. You can then manually trigger a run.

[wimdehaes]

@pdmuinck
It would require updating a lot of DAGs + you will have to add boilerplate code (to make the distinction between a prod and test env) to each DAG. While configuring an entire env is done only once and monkeyproof from then onwards.