Thoughts about tradeoffs between e g | Dagger | Page 1

This may be a case where you actually don't want dagger's aggressive caching, because you actually want to be checking the state of a remote resource every time. I suppose passing in Date.now() as an environment variable to the container could be a way to force its execution on the dagger side of things. But I'm having trouble coming up with any pros in favor of using a dagger container over the node SDK besides that those steps will actually appear in the DAG. Otherwise, that logic will still be running, and may impact the DAG, but Dagger doesn't know about it and won't visualize it for me.

#Thoughts about tradeoffs between e g