fresh-summer-6588712/01/2019, 5:43 PM
is "non-standard" and "against the grain". The expectation is that the .net program should be spawning the pulumi "engine" and not the other way around. And to be honest, I can see their point. There was also a couple of other comments • "I want to do other things in my program as part of deployment such as a db migration." • "I want to use this to define resources of my own services" This got me thinking a bit that it inverts things and turns pulumi into more of a platform and a bit more into orchestration which is bit of a fundamental architectural shift, afaik. Anyway, just thought it would be interesting to share.
tall-librarian-4937412/01/2019, 8:02 PM