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
  • #61
Closed
Open
Issue created Nov 05, 2024 by dockx thibault@tdockxMaintainer

[Orchestrator] - LifeCycle array supann is analyzed with static numbering

[Orchestrator] - LifeCycle array supann is analyzed with static numbering

An issue can present itself while analyzing the supann array during orchestrator processing, if the resource being analyzed is not first in the array returned by ldap, a potential miss match occur.

This must be iterated properly to avoid fix numbering in supann array.

NOTE : supann array return a string if only one value is present, and multiple (random key) array when multi-evaluated.

Assignee
Assign to
Time tracking