pulumi

History

Matt Ellis 9cdcd77015 Remove Pulumi.Host and CSI, in favor of `dotnet run` This feels more natrual, even if the code you end up writing to describe your application has a little more ceremony. We also don't have to worry about all the crazy things we likely would have had to worry about if we continued down the CSI path, or some path where we had a middle stage that reflection loaded an actual binary and invoked into it (I had a fear in the back of my mind that at some point we'd actually have to start using AssemblyLoadContext). This model is pretty easy to internalize, as well. The major change from the language plugin point of view is that instead of passing command line arguments to the executor, we just set a bunch of `PULUMI_XXX` env-vars, which parts of our system know how to use. Next up, Output tracking.	2018-06-21 10:50:08 -07:00
..
main.go	Remove Pulumi.Host and CSI, in favor of `dotnet run`	2018-06-21 10:50:08 -07:00

Matt Ellis 9cdcd77015 Remove Pulumi.Host and CSI, in favor of `dotnet run`

This feels more natrual, even if the code you end up writing to
describe your application has a little more ceremony. We also don't
have to worry about all the crazy things we likely would have had to
worry about if we continued down the CSI path, or some path where we
had a middle stage that reflection loaded an actual binary and invoked
into it (I had a fear in the back of my mind that at some point we'd
actually have to start using AssemblyLoadContext).

This model is pretty easy to internalize, as well.

The major change from the language plugin point of view is that
instead of passing command line arguments to the executor, we just set
a bunch of `PULUMI_XXX` env-vars, which parts of our system know how
to use.

Next up, Output tracking.

2018-06-21 10:50:08 -07:00

main.go

Remove Pulumi.Host and CSI, in favor of `dotnet run`

2018-06-21 10:50:08 -07:00