Skip to content
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

A way to test schedules without running them #80

Open
totalhack opened this issue Jan 31, 2023 · 3 comments
Open

A way to test schedules without running them #80

totalhack opened this issue Jan 31, 2023 · 3 comments

Comments

@totalhack
Copy link

Description

Apologies if I've just missed this, but is there a way to dry run schedules without actually executing the tasks? I have a number of schedules that are run in production and would like to be able to test configuration adjustments locally without actually executing tasks and without having to comment a bunch of stuff out. Ideally it would be a CLI or env var flag to specify this mode, and yacron would just print the tasks it would run.

Thanks.

@gjcarneiro
Copy link
Owner

No. The only thing you have right now is a --validate-config option, that checks that the configuration file is syntactically valid. But there's no dry run mode in yacron.

@andreas-wittig
Copy link
Contributor

Couple of days ago I had a similiar question to [gjcarneiro].
My issue could be solved with enabled=[true, false] ; i.e. whether a schedule is active or not.
[totalhack]s issue is not the same, but "sounds similiar".
A possible extension could be enabled=[true, false, test] => with test the desired magic could be done.

@totalhack
Copy link
Author

@andreas-wittig adjusting your config that way doesn't scale well during development. A global CLI flag or env var setting would make more sense in this case IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants