Currently, when a stateless dataflow is created, a ParameterProvider is supplied, which the engine can use to retrieve parameterized values for the dataflow.
However, it will make sense going forward to allow for a ParameterProvider to be defined outside of the scope of what is provided by default in the stateless api. For example, there may be a desire to integrate with a a secret store provided by a public cloud service, etc. Such a capability would need to be encapsulated in a NAR instead of added to the root class path.
As such, we need to refactor the stateless api such that instead of providing a ParameterProvider, we instead introduce a notion of a ParameterProviderDefinition, and then include a List of ParameterProviderDefinitions as part of the Dataflow Definition.
In this way, we can make the parameter retrieval far more flexible and powerful.