Statically expose pod dependencies — idea/proof of concept

I have mostly been thinking about pods inside boot-tasks which are opaque to the user of the task. What you describe seems like a situation where you create the pods yourself and thus are aware/in control what goes into them.

I do agree however that an API to make a pod from a deps.edn file (+ any parameters like profiles) would be very nice.