Hi, I wanted to upgrade our pulumi-ovh provider ( to be synced with our terraform provider, as usual). When I executed the upgrade command

upgrade-provider ovh/pulumi-ovh

, I have an error:

error: failed to gather package metadata: problem gathering data sources: 1 error occurred:

* Pulumi token "ovh:CloudProjectDatabase/getIpRestrictions:getIpRestrictions" is mapped to TF provider data source "ovh_cloud_project_database_ip_restrictions", but no such data source found. Remove the mapping and try again

make: *** [Makefile:59: tfgen] Error 255

After analyzing our Terraform provider, it appears that the datasource have not disapeared BUT we are currently migrating our resources and datasources to use the new

terraform-plugin-framework

instead of old

terraform-plugin-sdk/v2

This is the new SDK that should and will be used to declare new resources/datasources. The terraform provider now uses a mux server that allows to have both SDKs used at the same time (see: https://github.com/ovh/terraform-provider-ovh/blob/master/main.go#L33-L43). So is it possible to say to Pulumi to take in account resources and datasources declared with the old and the new terraform plugin framework? FYI, for the moment, we only declared in the new way this datasource: https://github.com/ovh/terraform-provider-ovh/blob/master/ovh/provider_new.go#L163 but all of the others are still declared in the old way: https://github.com/ovh/terraform-provider-ovh/blob/master/ovh/provider.go#L50 Is it possible to help us in this issue, because right now we can’t upgrade.sync the pulumi provider. Thanks 🙂

@thankful-match-46035 in a case where you are migrating from old to new in TF land, you can leverage the multiplexer, aka "muxer" of our tf-bridge framework. Here is an example where you see both providers muxed on the Pulumi side: https://github.com/pulumiverse/pulumi-buildkite/blob/c3cd7cc214e71d6d5b7ab38555a2050b785b8dde/provider/resources.go#L60-L63

I would look at the guide for How to Upgrade a provider that has partially migrated to the Plugin Framework. If you get stuck, please reach out here again.

Thanks I’m trying to follow the guide, step by step ^^ Question: is it

pfbridge

or

tfbridge

?

🤦 The examples don’t include import statements. The examples assume these imports:

import (
    pfbridge "<http://github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge|github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge>"
    "<http://github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge|github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge>"
)

and what is the import for “provShim” ?

Whatever the correct import is to access the PF provider struct of the provider you are bridging.

For the moment I wrote this but I still have an error in

ovh.New(),

line

I can’t find

ovh.New()

. What is the return type of

ovh.New()

?

I finally fixed the resources.go file I updated the tf-gen main.go file And updated the main.go with tfbridge call but unfortunately when I am launching the upgrade-provider script, I have an error “error: ProviderInfo.MetadataInfo is required and cannot be nil”

You need to add a metadata file and point ProviderInfo to it. This is called out unfortunately subtly in the upgrade guide:

> Muxed providers need an accompanying

MetadataInfo

. If the provider did not have one set up, this is the time to do so.

How to set this up is shown in “How to Upgrade a Bridged Provider to Plugin Framework” (step 4).

I updated the code with MetaDataInfo and go embed bridgeMetadata (and added missing import embed), unfortunately still have an issue

You also need to create the empty file for

go:embed

to pick up:

echo {} > cmd/pulumi-resource-ovh/bridge-metadata.json

fixed with //go:embed cmd/pulumi-resource-ovh/bridge-metadata.json Documentation is not easy to understand and follow 😞

Documentation is not easy to understand and follow 😞

I’m sorry. We know and are working on it.

I’m executing again (for the xx time, I didn’t count ^^) the upgrade-provider command and hope everything should be ok 🤞

@thankful-match-46035 our registry publishing isn't instantaneous. We check for new releases twice a day. Here is the PR for your new release: https://github.com/pulumi/registry/pull/4005 I'll merge it together with some other ones this morning.

thanks for the information

I will have to leave this to @ancient-policeman-24615 or @enough-garden-22763 for further investigation.

From the error message, it looks like the version wasn’t correctly linked into the executable. I’m taking a look now.

Top, thanks! I merged the commits and published a new release 0.37.1 is now working