thank you @brainy-caravan-45245! @enough-garden-22763 Here we are 👍

@big-architect-71258 welcome!

@prehistoric-kite-30979 @narrow-match-14013 welcome!

@prehistoric-kite-30979 long time no see 😁 👍🏼

@enough-garden-22763 just working on the support for PF in the Cookiecutter Pulumi Provider template. When I use the template to wrap the current Hashicorp TLS provider (branch master, because that's the only one using PF 1.1.1) and I try to generate

tfgen

via

make tfgen

, compilation fails with following error:

(cd provider && go build -o /tmp/pulumi-tls/bin/pulumi-tfgen-tls -ldflags "-X <http://github.com/pulumiverse/pulumi-tls/provider/pkg/version.Version=0.0.1-alpha.1675966033+870bfb04.dirty|github.com/pulumiverse/pulumi-tls/provider/pkg/version.Version=0.0.1-alpha.1675966033+870bfb04.dirty>" <http://github.com/pulumiverse/pulumi-tls/provider/cmd/pulumi-tfgen-tls)|github.com/pulumiverse/pulumi-tls/provider/cmd/pulumi-tfgen-tls)>
# <http://github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge|github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge>
/home/user/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.1.0/tfbridge/naming.go:33:44: undefined: tfgen.Renames
/home/user/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.1.0/tfbridge/provider.go:86:20: undefined: tfgen.Renames
Makefile:27: recipe for target 'tfgen' failed

Do I reference a wrong version of

pulumi-terraform-bridge/pf

? I didn't experience this error when I manually wrapped the MSSQL provider.

Thank you @big-architect-71258 also for reporting issues with custom type. I filed in https://github.com/pulumi/pulumi-terraform-bridge/issues/803

https://github.com/pulumi/pulumi-terraform-bridge/releases/tag/pf%2Fv0.2.0 is out

Folks a quick note on the above - I'd like to release pulumi-random with this version, there's some build system hiccups that we're working through but that will come shortly. If all goes will with it we plan to release pulumi-tls on PF also. This gets some real-world validation for the bridge.

Beyond that, to prioritize what to work on first from https://github.com/pulumi/pulumi-terraform-bridge/issues/744 I'd like to be open to suggestions from actual users and feedback from the real world. So please feel free to open issues or just ask here! I'll also keep posting release announcements here. :thank-you: 🙏

set the channel description: Discussions and early adopter support for pulumi/pulumi-terraform-bridge functionality for supporting Terraform Plugin Framework based Terraform providers in Pulumi. Status: preview.

pulumi-random v4.11.1 is out utilizing the latest Plugin Framework enabled bridge.

pulumi-tls v4.9.0 is out on the same version of the bridge pf/0.2.0

Hey wondering if this has anything to do with how the bridge works. I've got an issue where if i have multiple levels of

pulumi.interpolate

pulumi throws an error:

error: Preview failed: objectEncoder failed on property "url": Expected a string, got: {&{{<http://vm-4liajfa3.staging.azure.tetrate.com/}}}>

If i wrap the whole thing in an apply it works though. For example:

pulumi.output(args.endpoint).apply(
                    (endpoint) =>
                        new checkmate.HttpHealth(
                            `${this.pulumiName}-check-endpoint`,
                            {
                                timeout: 1000 * 60 * 10, // 10 min, to allow for DNS to propagate (2 x TTL)
                                interval: 1000 * 2, // 2s
                                consecutiveSuccesses: 100,
                                url: endpoint,
                            },
                            { dependsOn: this.resources },
                        ).id,
                )

Any ideas?

There's a small set of bugfix releases. pf/v0.2.1 and pulumi-random v4.11.2 and pulumi-tls v4.9.1

Folks we had to undo the tls release one more time. The issue is https://github.com/pulumi/pulumi-tls/issues/173 - it looks like it should have been a major version bump since upstream doesn't provide a safe upgrade path. Moreover, the workarounds from upstream didn't work at all for making the upgrades safe to Pulumi without ignoreChanges (coming soon) support.

Tagging pf/v0.3.0 with ignoreChanges support.

🗒️ Pulumi has a winter refresh week all next week so we might not be able to respond until Feb 27.

Does anyone have a good repro for https://github.com/pulumi/pulumi-terraform-bridge/issues/812 ? I'd love to have that fixed but can't seem to reproduce.

@enough-garden-22763 Anton, sorry to bother you again with the nasty issue around invalid default values in the Azure Classic provider, but it seems the PR 768 to the Pulumi Bridge didn't fix all cases in which the Bridge enriches the data transferred to the Terraform Provider with default values. Please have a look at my last comment with default https://github.com/pulumi/pulumi-terraform-bridge/issues/720#issuecomment-1458013885

pf/v0.4.0 is out

pf/v0.5.0 is out thank you @narrow-match-14013 again for the repro on #812!

woo!

hey might be wrong channel for this but i seem to always get an error along the lines of:

warning: resource plugin checkmate is expected to have version >=0.1.5, but has 0.0.1; the wrong version may be on your path, or this may be a bug in the plugin

and i'm not sure where pulumi is getting that version number. my bridge project has version 0.1.5 and i dont see 0.0.1 anywhere in the code. everything works fine, just wondering why pulumi thinks the versions dont match

and this is what i have installed

% pulumi plugin ls | grep checkmate
checkmate     resource  0.1.5    58 MB   38 minutes ago  35 minutes ago

Hey @enough-garden-22763, is there a list of features from the plugin-framework that aren’t currently supported?

pf/v0.6.0 small release that lets you observe logs emitted against TF APIs through Pulumi logging, and fixes GetMapping infrastructure used by tooling such as tf2pulumi, specifically I'm looking to patch pulumi-random to get it working with tf2pulumi again.

Working on Set support.

@enough-garden-22763any time frame when custom objects are supported?