worried-city-86458
05/11/2021, 8:55 PMI'm using my own generic host with the dotnet automation api, wiring up the usual config, logging, dependency injection etc, and was wondering / hoping this language server could be integrated better with such a generic host so that I have full control of the previous concerns. Thoughts?
bored-oyster-3147
05/11/2021, 8:57 PMworried-city-86458
05/11/2021, 9:02 PMbored-oyster-3147
05/11/2021, 9:12 PMPulumiFn
. The current architecture is kind of relying on the fact that the pulumi program to language host is 1:1 - if it was a long lived language host, than we would need additional services to handle passing in the pulumi program to the language host and we would need to figure out a way for the language host to select the appropriate pulumi program
Ultimately I think attaching it to an existing web host is kind of antithetical to the current architecture, and may be wasted effort since the future goals are to remove the Automation API's CLI-dependency which would mean the web host we are spinning up may no longer be necessary when that happens anywaysPulumi.Automation.AspNetCore
. I personally don't really see this happening, because like I said the language host is an implementation detail and bringing any of that or too much of that into the Public API would tie them to it. Could tag some pulumi folks here to get their inputworried-city-86458
05/11/2021, 9:33 PMbored-oyster-3147
05/11/2021, 9:55 PMworried-city-86458
05/11/2021, 10:31 PM