Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-orchestrator fusiondirectory-orchestrator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-orchestratorfusiondirectory-orchestrator
  • Issues
  • #39
Closed
Open
Issue created Mar 18, 2024 by dockx thibault@tdockxMaintainer

[Orchestrator] - New endpoint notifications in order to manage notifications tasks

Here below a list of step by step requirements for the above concept to be feasible:

  • A new endpoint “notifications”
  • Making sure the tasks notification is well processed based on its cycle of repetition.
  • Treat every subtasks and send the notification if required + update status of the subtask.
  • Remove the subtasks if no attributes listed match the alert specified in the main task.

A design document can be found about notifications here

Assignee
Assign to
Time tracking