Closed as not planned
Closed as not planned
Description
Description
What problem are you trying to solve?
As apart of planned events, there are instances in which budgets should be schedule-able within a human readable format that can be easily understood and reasoned about.
This feature should also follow the current standard of minimal ("most restrictive") budgeting when multiple budgets are defined with overlapping timeframes or crontab schedules.
How important is this feature to you?
This feature would enable operators to schedule budgets for many one-off events in the future when they are known about, without having to create and compare complex crontab definitions against one another.
- 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
Activity