pulumi/sdk
Matt Ellis d7575072f2 Do not use relative path when launching dynamic provider
Previously, we assumed that the dynamic provider was located in
`./node_modules/@pulumi/pulumi/../` which is correct in the majority
of cases. However, tools like lerna or yarn workspaces (or custom
workflows) allow the node_modules folder to be located elsewhere on
disk, and node will still find it because of its algorithm for module
resolution.

So, do what we do in the language host itself, first launch node and
ask it to tell us where it resolves a require statement to on disk and
then launch node against that script.

Fixes #2261
2018-12-05 13:45:06 -08:00
..
go Use Infof instead of Infoln when we have format strings 2018-11-08 14:11:52 -08:00
nodejs Do not use relative path when launching dynamic provider 2018-12-05 13:45:06 -08:00
proto Fix, formalize and add tests for property rewrites (#2187) 2018-11-12 09:26:31 -08:00
python Flush stdout and stderr on abnormal lang shutdown (#2226) 2018-11-19 17:59:01 -05:00
README.md Update stale README 2018-06-30 09:55:12 -07:00

README.md

Pulumi Language SDKs

This directory contains the Pulumi SDKs for all supported languages.

Please see the respective READMEs for information about installing and using these libraries:

The language providers work by implementing gRPC interfaces defined in proto/.