Orchestrator should read the property checkExistsDataToProcess from pipeline's manifest
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
The orchestrator should read the value for checkExistsDataToProcess from each pipeline, from the manifest of pipelines.
If the instance of the Carol App on the orchestrator has the checkExistsDataToProcess enabled, it should read from the manifest the value for checkExistsDataToProcess for each pipeline it is going to process.
- Orchestrator has the
checkExistsDataToProcessenabled.- If the pipeline on manifest of pipeline has a value defined for
checkExistsDataToProcess, it should consider this value. - If the pipeline on manifest of pipeline does not have this setting, it should consider the value from the orchestrator (keep it enabled).
- If the pipeline on manifest of pipeline has a value defined for
- Orchestrator has the
checkExistsDataToProcessdisabled- It will keep
checkExistsDataToProcessdisabled by default.
- It will keep
06 - ACCEPTANCE CRITERIA:
- Behavior described on
goal.
Activity
Show:
Details
Priority
HighAssignee
Ingo Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEW
Due Date
12 March 2024
Fix versions
CAPL_4.00
Components
SQL_PIPELINES | ORCHESTRATOR
Created
19 February 2024, 21:14
Updated
12 March 2024, 21:29
More fields
Created: 20 February 2024, 00:14
Updated:
13 March 2024, 00:29
Oi@Ingo Wagner Estou preparando material para a agenda de updates da carol com nossos clientes, só confirma para mim se tivemos implementação em código, pois não vejo branch e commit neste card.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.