But, just my 2 cents here, the

session.run

api seems to match perfectly the use cases, if it returned all the datasets data are a result from a node/pipeline/set of inputs or a list of the wanted outputs. Now,

session.run

shouldn't change, obviously, but the api and the arguments in the signature seem very ergonomic to me.