constraint on pipeline env map

[hrishin]

Pipeline env map should refere to only one environment of each type.

example.

env_map1 {
   .......
   environments: [
         env1
         env2
   ]
} 

Where env1 is type of stage and env2 of type of production.
What if use selects two stage types env while creating pipeline envs map, where env1 and env2 are type of stage

If this is a valid constraint, then API should do validate env map before creating/updating it.

[chmouel]

This is all coming from launcher (ie it will enforces it) but we can add a constraint if needed,

[hrishin]

Agreed thats one option.
If pipeline env map is the source of truth in build service, then it's better to add a constraint on the build API side?
All API consumer (UI, app creation service) would behave consistently in that way.