I don’t think there is an elegant solution to this at the moment. You rightly point out the big issue
I can’t see a generic way to use the ‘Pipeline Execute’ snap as the types and numbers of pipeline parameters will vary.
Since there isn’t a way to dynamically pass the pipeline parameters I don’t think there is much you can do.
A less elegant approach could be to devise some kind of pipeline parameter convention. Like all pipelines would accept n
parameters and you’d pass n
even when the pipeline uses only 3. There could be other conventions you use, but you’d have to consider the tradeoffs with what you’re trying to achieve.
Personally I think this could be an interesting enhancement to the product, so I’ll share with product owners to see what they think.
Could you talk a bit more about what is motivating the need to re-run a pipeline?
Have you taken a look at resumable pipelines before? Maybe that is something that could help your use case?
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/721944618/Resumable+Pipelines