Orchestrator: specify interval between groups customized for cron expression
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
We need to better control the interval during the weekends, for this case, we need to allow to specify the parameter waitBetweenGroups for each cron expression:
waitBetweenGroups: 120000,
waitBetweenGroupsForCron: {
'*/2 * * * MON-FRI': 30000,
},
It will try to load from the waitBetweenGroupsForCron, if it has no specific configuration, we will use the default value “waitBetweenGroups
“. If it does not have a default value, the orchestrator applies 1 second as default (existing rule).
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Allow to define
waitBetweenGroupsForCron
. for each cron expression. - It will read the default configuration (
waitBetweenGroups
) if it does not have a specific configuration for the cron expression.
@Robson Thanael Poffo ,
@Gabriel DAmore Marciano , @Ingo Wagner , @Douglas Coimbra Lopes
This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-02-12, 2024-03-04
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Jonathan Willian Moraes @Chámam Diomede Caires We will wait for the product team’s tests before closing this card.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-02-12
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.