pf/v0.7.0 is out with set support.

pf/v0.7.1 is out - we've been hard at work to support hybrid sdkv2/pf based providers and use our own work in pulumi-aws, pulumi-gcp, pulumi-cloudflare to ensure the resources based on Plugin Framework are available. Lots of fixes come from this experience of trying to use the PF bridge on larger providers. Calling out a breaking change - https://github.com/pulumi/pulumi-terraform-bridge/pull/964 - we try to minimize these but went ahead with this one as it greatly simplifies the plumbing for hybrid provider use cases.

@enough-garden-22763 saw that you created pf/0.8.0 release already 🙂

Hey folks does anyone have done some work to compile pulumi from terraform plugin framework??

pf/v0.8.1 is out - this is a bugfix release (sorry I fat-fingered v0.8.0 so now there's a bit of a version gap). We've been hard at work supporting larger providers that use a mix of SDKv2 and PF resources, targeting pulumi-aws, pulumi-gcp and pulumi-cloudflare, leading to bug discovery and fixes as we go. This remains top goal for the current iteration (3w starting this week). As of today https://github.com/pulumi/pulumi-terraform-bridge/issues/1032 and https://github.com/pulumi/pulumi-terraform-bridge/issues/1028 are top of mind known blockers.

Need some help figuring out the order of operations here. In the README it shows that

pulumi-tfgen-myprovider

needs to have the

bridge-metadata.json

embedded, but is also the thing that generates it. I upgraded from pf/v0.6.0 to v0.8.1 and i'm hitting an error presumably because the bridge format has changed, but i can't regenerate it

error: fatal: failed to Init GRPC to register RPC handlers: failed to create resource provider: [pf/tfbridge] ProviderInfo.BridgeMetadata has no required 'renames' value

@narrow-match-14013 PR 964 https://github.com/pulumi/pulumi-terraform-bridge/pull/964 introduced this breaking change and there's documentation how to change the code as well. But be aware of issue https://github.com/pulumi/pulumi-terraform-bridge/issues/1019 😉

v0.9.0 is out - special thanks to @big-architect-71258 for contributions toward DefaultInfo support.

v0.9.1 - looks like I forgot announcing this small bugfix release to fix logging annoyance. We're moving forward with deploying Plugin Framework code into production as part of regular Pulumi providers. Currently 6 providers are using this version as you can see here https://github.com/pulumi/pulumi-terraform-bridge/issues/981 - we're starting with Tier2 providers to gain confidence but the plan is to scale it to Tier1 providers like pulumi-gcp and pulumi-aws.

v0.9.2 bugfix release is now rolled out to all Pulumi-maintained providers to compensate for

error: rpc error: code = Unknown desc = config value 'token' mismatch between servers 1 and a previous server

v0.10.0 is not yet rolled out but I'm tagging it before the long weekend so it's available. There's some feature progress most notably around validating provider and resource configurations, calling PreConfigureCallback if defined and presenting errors better.

ive been asked to rename this channel to

#package-authoring

, so imma do that

has renamed the channel from "plugin-framework" to "package-authoring"

Hey everybody I am trying to create a pulumi package and trying to run

make build install

but there is something weird with the versions, so running

pulumictl get version

returns 0.0.1-alpha.1685580978+4aae2ffb.dirty, where is that coming from and how do I change it?

Hello all, we tried to create a bridged provider from our terraform provider, but we think we may be using a newer version of the terraform SDK. Looking more closely at documentation, we used the terraform-plugin-framework to develop our provider and pulumi seems to only support creating a bridge provider for terraform providers developed with the older SDK - https://github.com/pulumi/pulumi-terraform-bridge#pulumi-terraform-bridge https://developer.hashicorp.com/terraform/plugin/framework-benefits Is this true? I wonder how we can move forward from here.

v0.11.0 closes the gap in Private State support and a few bugs discovered thanks to the community provider https://github.com/Authress/pulumi-authress - pluginDownloadURL should now work properly, and failing to set required provider properties should surface meaningfully though Pulumi CLI.

What is the correct list of people available for a pull request review in Pulumiverse? Are these the people who are designated as members of the board for Pulumiverse? https://github.com/pulumiverse/.github/blob/main/governance/board.md #pulumiverse @limited-rainbow-51650

Hey folks, I have question regarding Pulumi Bridge for Terraform Plugin Framework. There is one behavioral I can't explain and I am not totally sure if it's bug or I am doing something wrong. So I have a few data source, There is no input. They using your identity baked in into profile to retrive data. And all work fine of tf side., but when same data provider gets generate in pulumi I do observer a diff between them and another data sources. First of all they hav only gat method. Usually any data sorce will have regular call and wrapped into with pulumi like

getResource

and

getResourceOutput

Those data source also throwing this error:

panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x1b6c6e8]
    goroutine 25 [running]:
    <http://github.com/pulumi/pulumi-terraform-bridge/pf/internal/convert.(*encoding).NewDataSourceEncoder(0xc0003713a0|github.com/pulumi/pulumi-terraform-bridge/pf/internal/convert.(*encoding).NewDataSourceEncoder(0xc0003713a0>, {0xc0003b0408, 0x16}, {0xc000d50e10, 0x0, {0x0, 0x0, 0x0}})
    	/root/.cache/gomodcache/github.com/pulumi/pulumi-terraform-bridge/pf@v0.8.1/internal/convert/encoding.go:96 +0x88
    <http://github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).datasourceHandle(0xc00046d600|github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).datasourceHandle(0xc00046d600>, {0x38679d0, 0xc000d50de0}, {0xc0003b0408, 0x16})
    	/root/.cache/gomodcache/github.com/pulumi/pulumi-terraform-bridge/pf@v0.8.1/tfbridge/provider_datasources.go:53 +0x1eb
    <http://github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).InvokeWithContext(0xc00046d600|github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).InvokeWithContext(0xc00046d600>, {0x38679d0?, 0xc000d50c60?}, {0xc0003b0408, 0x16}, 0x2dc013d8?)
    	/root/.cache/gomodcache/github.com/pulumi/pulumi-terraform-bridge/pf@v0.8.1/tfbridge/provider_invoke.go:41 +0x176
    <http://github.com/pulumi/pulumi-terraform-bridge/pf/internal/plugin.(*providerServer).Invoke(0xc000bb32f0|github.com/pulumi/pulumi-terraform-bridge/pf/internal/plugin.(*providerServer).Invoke(0xc000bb32f0>, {0x38679d0, 0xc000d50c60}, 0xc00047ef00)
    	/root/.cache/gomodcache/github.com/pulumi/pulumi-terraform-bridge/pf@v0.8.1/internal/plugin/provider_server.go:505 +0x11d
    <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Invoke_Handler.func1({0x38679d0|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Invoke_Handler.func1({0x38679d0>, 0xc000d50c60}, {0x2f69500?, 0xc00047ef00})
    	/root/.cache/gomodcache/github.com/pulumi/pulumi/sdk/v3@v3.69.0/proto/go/provider_grpc.pb.go:480 +0x7b
    <http://github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1({0x38679d0|github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1({0x38679d0>, 0xc000d50a20}, {0x2f69500, 0xc00047ef00}, 0xc000472940, 0xc000421aa0)
    	/root/.cache/gomodcache/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x3e8
    <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Invoke_Handler({0x30eff40|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Invoke_Handler({0x30eff40>?, 0xc000bb32f0}, {0x38679d0, 0xc000d50a20}, 0xc0008475e0, 0xc00078c080)
    	/root/.cache/gomodcache/github.com/pulumi/pulumi/sdk/v3@v3.69.0/proto/go/provider_grpc.pb.go:482 +0x138
    <http://google.golang.org/grpc.(*Server).processUnaryRPC(0xc0009905a0|google.golang.org/grpc.(*Server).processUnaryRPC(0xc0009905a0>, {0x3872ca0, 0xc000baa9c0}, 0xc000c1cc60, 0xc000bb3380, 0x4b4d0a0, 0x0)
    	/root/.cache/gomodcache/google.golang.org/grpc@v1.54.0/server.go:1345 +0xdf3
    <http://google.golang.org/grpc.(*Server).handleStream(0xc0009905a0|google.golang.org/grpc.(*Server).handleStream(0xc0009905a0>, {0x3872ca0, 0xc000baa9c0}, 0xc000c1cc60, 0x0)
    	/root/.cache/gomodcache/google.golang.org/grpc@v1.54.0/server.go:1722 +0xa36
    <http://google.golang.org/grpc.(*Server).serveStreams.func1.2()|google.golang.org/grpc.(*Server).serveStreams.func1.2()>
    	/root/.cache/gomodcache/google.golang.org/grpc@v1.54.0/server.go:966 +0x98
    created by <http://google.golang.org/grpc.(*Server).serveStreams.func1|google.golang.org/grpc.(*Server).serveStreams.func1>
    	/root/.cache/gomodcache/google.golang.org/grpc@v1.54.0/server.go:964 +0x28a

@dry-potato-52542 I think it's worth trying to update to v0.11.0 of

pulumi-terraform-bridge/pf

. @enough-garden-22763 and @ancient-policeman-24615 are working heavily on PF support. So v0.8.1 is pretty dated 😏

@dry-potato-52542 just saw you tried upgrading. Ignore my message.

v0.11.1 small bugfix addresses the compilation error above. With this fix Go should pull correct dependencies and your code should now compile.

Hello everyone! I'm resharing this message from the #pulumiverse as we're keenly interested in getting feedback from end users on a tool we're shipping. Details in the message below, the summary: fully automated pull requests to upgrade TF providers. https://pulumi-community.slack.com/archives/C037PV12W6L/p1686171550846699

Celebrating a new community provider party pizza https://github.com/pulumiverse/pulumi-mssql

Hi all, could there be an issue with the latest release of Pulumi where it makes plugins running in child process believe they should print color output? I am seeing this error since v3.70 where it looks like

@grpc/grpc-js

is correctly printing the port, but unfortunately it's being wrapped in ANSI color codes...

pulumi:providers:pulumi-nodejs default  error: pulumi-nodejs (resource) plugin [/opt/homebrew/bin/pulumi-resource-pulumi-nodejs] wrote a non-numeric port to stdout ('0'): strconv.Atoi: parsing "\x1b[33m65010\x1b[39m": invalid syntax

Hey folks! If you're authoring Plugin Framework based providers, we have a breaking change in v0.12.0 of the bridge. We're making this break to make it possible to use

ComputeDefaults

and

AutoAliasing

, and we've also made PF based providers use the same

tfbridge.ProviderInfo

as SDKv2 providers. Implementing this, you'll modify your

Provider

constructor (typically in

resources.go

) to return or use the original

tfbridge.ProviderInfo

instead of using a plugin framework (

pf/tfbridge

) version. You'll pass the upstream provider to the

P

field, as with SDKv2 providers, but you'll use

pf.ShimProvider()

instead of

shimv2.NewProvider

. We have examples in our unit tests here: https://github.com/pulumi/pulumi-terraform-bridge/blob/adfd7f99c35316d683a6fcd562f816ac3c765bb2/pf/tests/internal/testprovider/random.go#L64-L66

Celebrating a new provider: https://github.com/dirien/pulumi-fly 🎉

I am having a hard time finding documentation on how to author providers. Currently have based off of https://github.com/pulumi/pulumi-go-provider Sadly this is for internal use, so unable to share much… But I need to instantiate an API client with credentials from configuration. I would prefer to do this only once, can I do that? I would like a config option for

environment

which should be an enum, how do I do that? And lastly, I am getting this weird error:

panic: invalid Go source code:

amma/resources/init.go

: 35:18: expected operand, found '.' (and 1 more errors)

I cannot identify the cause 😕

Ahh, it seems to be because I split my resources into multiple packages. Is that really a problem? I cannot imagine that would be the case.

Is there an actual version of pulumi-provider-boilerplate? It seems that the provided deployment templates aren't working properly with the manual builds in the makefile.

I have a question about the

ExtraFunctions

field in in the

ProviderInfo

struct inside TF Bridge. How is it supposed to be used? Backgroud: I wanna add a

getClientToken

function to the Azure Classic provider. Just like the function which is available in the Azure Native provider. I think I created the declaration correctly because

tfgen

creates the `schema.json`file with the added function definition without an error.

ExtraFunctions: map[string]pschema.FunctionSpec{
			"azure:core/getClientToken:getClientToken": {
				Description: "Use this function to get an Azure authentication token for the current login context.",
				Inputs: &pschema.ObjectTypeSpec{
					Type:        "string",
					Description: "Optional authentication endpoint. Defaults to the endpoint of Azure Resource Manager.",
				},
				Outputs: &pschema.ObjectTypeSpec{
					Type:        "string",
					Description: "OAuth token for Azure Management API and SDK authentication.",
				},
			},
		},

"azure:core/getClientToken:getClientToken": {
            "description": "Use this function to get an Azure authentication token for the current login context.",
            "inputs": {
                "description": "Optional authentication endpoint. Defaults to the endpoint of Azure Resource Manager.",
                "type": "string"
            },
            "outputs": {
                "description": "OAuth token for Azure Management API and SDK authentication.",
                "type": "string"
            }
        },

But now I'm stuck, because I don't know where to put the function implementation. Can someone help me here? I found this PR of @microscopic-pilot-97530 that sheds some light on this. But neither I know how to create a multiplexed provider nor do I know how to create an "overlay" 😀 https://github.com/pulumi/pulumi-terraform-bridge/pull/625