As Carol Admin I should be able to manage Orchestrator

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):

Allow the Carol Admin to manage Orchestrator by:

  • Restarting it (forcing to reload the manifests).
  • Previewing instances running (manifests processing data through the new orchestrator)
    • Tasks with:
      • "script": "carolapp",.
      • Connector Groups: connector group name, list of pipelines.
  • Preview the last task and the existing cron expressions for each instance (manifest) of the orchestrator.
  • Task’s Properties
    • Carol App Name
    • "cron": "*/30 * * * *",
    • "tenantGroups": 10,
    • "waitBetweenGroups": 300000, (milliseconds)
    • Pipeline Name
    • Tenants
    • Additional Details (configurations from the manifest file: saveCds, saveBQ, SQL command, etc)
curl -X GET 'https://frontend.carol.ai/carol-orchestrator/tasks/status' -H 'accept: application/json' -H 'content-type: application/json' -H 'authorization: TOKEN' --compressed

04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):

https://www.figma.com/file/FiL1iRG6RPjuNCgVzgGqvaZ3/%F0%9F%9F%A3-Carol-3.0?type=design&node-id=34737-122222&mode=design&t=wsZMdltNEATWhCdH-4

06 - ACCEPTANCE CRITERIA:

  • Preview the current status of the orchestrator:
    • Carol Apps registered.
    • Pipelines registered
    • Last date/time the orchestrator reload the manifest and tenants related to the pipeline (not available today)
    • Manifest related to the schedule
    • Cron expression
    • Tenants with the app associated
  • Ability to restart the orchestrator
  • Ability to reload the orchestrator configuration by carol app.

UI:

  • Create new tab “Orchestrator” on Carol Admin
  • Allow to Restart Orchestrator
  • Each line must show an App (link to navigate to the app inside Carol - access rules applied)
  • By clicking on the line it’ll open the list of pipelines of this app.
    • By clicking on the line of the pipeline it must open an side panel with the list of Tenants on this pipeline.
  • The App Manifest button must open an side panel with the manifest and allow to navigate to Github.

Activity

Automation for Jira 13 May 2024, 14:21 Jira Internal Users

Esta issue foi automaticamente movida para WAITING DEPLOY, pois a issue relacionada de QA regression também chegou ao status WAITING DEPLOY (PR foi mergeado na branch master no Github).

Automation for Jira 8 May 2024, 10:59 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 8 May 2024, 10:59 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 8 May 2024, 10:59 Jira Internal Users

Esta issue foi automaticamente movida para REGRESSION, pois o PR foi mergeado na branch QA no Github.

Automation for Jira 7 May 2024, 11:45 Jira Internal Users

Esta issue foi automaticamente movida para TESTED & MERGED, pois o PR foi mergeado na branch Develop no Github. PR aprovado por .

Automation for Jira 6 May 2024, 18:46 Jira Internal Users

@MARCOS STUMPF ,
@Gabriel DAmore Marciano , @Ingo Wagner ,

Este issue foi planejada para ser entregue até 2024-05-27. Você pode confirmar consultando o campo Due Date desta issue.

Data já planejadas para esta issue: 2024-05-06, 2024-05-27

Se o campo External Issue Link estiver preenchido com o link de uma issue válida no Jira Produção o cliente também será notificado no Jira Produção.

Automation for Jira 3 May 2024, 16:49 Jira Internal Users

Esta issue foi automaticamente movimentada para REVIEW, pois o PR (não DRAFT e não WIP) foi criado no Github.

feat: https://totvsideia.atlassian.net/browse/CAPL-5778#icft=CAPL-5778 orchestrator details in carol-admin

Automation for Jira 25 April 2024, 13:36 Jira Internal Users

@MARCOS STUMPF ,
@Pedro Buzzi ,
@Geny Isam Hamud Herrera ,
Esta issue foi planejada para ser entregue até 2024-05-06. Você pode confirmar consultando o campo Due Date desta issue.

Datas já planejadas para esta issue: 2024-05-06

Se o campo External Issue Link estiver preenchido com o link de uma issue válida no Jira Produção o cliente também será notificado no Jira Produção.