Hi! I'm working on packaging the Pulumi ecosystem...
# general
c
Hi! I'm working on packaging the Pulumi ecosystem in nixpkgs, and I'm not finding any documentation explaining how to use pulumi-terraform-bridge to wrap an already-built terraform provider (which we have many already packaged)
e
Although nowerdays we'd recommend using pulumi.com/docs/…/any-terraform-provider for most providers.
c
essentially, I'm implementing an equivalent to
pulumi add terraform-provider
, for users (like myself) which rely on providers from nixpkgs. That's in contexts where nix is already used to ensure everyone has the same version of every tool (and every dependency, recursively) so using
pulumi add
violates that expectation
in practice, I need to build ahead-of-time (and with known versions etc.) the providers and Python/JS/whatever SDK, without network access (the terraform provider and its source code are available as dependencies though)
Does
pulumi add terraform-provider
do something different than the bridge?
e
pulumi add terraform-provider
is the dynamic bridge, so rather than linking to the terraform code it downloads the terraform plugin executable, and talks to it via grpc translating pulumi rpc commands into terraform rpc commands.
c
I see. Is there a way to point it at an already-downloaded tf plugin, and to build the SDK(s) ahead of time?
e
You can point it to a local binary
c
Thanks!