Rudder

This is a very, very clear limitation of today parameters.

There is a reason, which that doing reporting on that is hard(er - at least).

Basically, we have two options:

- either say we are waiting for one parameter, and that is not good because we really want to know what package was in error, not a "everything work / nothing worked"
- or have reports for each item. This is a problem at least for client-side generated lists, because well, we don't know what we are expecting on the server.

So we could limit to only server side list, no ? Well, in that case, it leads to inconsistancy in behavior between different kinds of parameters (env variables, data from inventory, etc).
See for ex. #5506 and all its related tickets.

So we are trying (very hard) to find an acceptable generalisation of that :)

The "Variables (any)" technique allows defining strings or dicts variables.