[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.

changed milestone to %FusionDirectory Orchestrator 1.1

added universite-orleans label

assigned to @tdockx

added PJ1802-0188 label

Time tracking in client side

added Bugs label

created branch 61-orchestrator-lifecycle-array-supann-is-analyzed-with-static-numbering to address this issue

mentioned in merge request !62 (closed)

created branch 61-orchestrator-lifecycle-array-supann-is-analyzed-with-static-numbering-2 to address this issue

mentioned in merge request !63 (merged)

closed

added Fixed label

removed Bugs label