You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is by design. We went with a different architecture for our provider because having all code in a single package was not sustainable from a code ownership point of view. Also this code was not at all covered by any backward compatibility outside of using it with terraform/opentofu. I'm not sure to understand why pulumi is using this import that was not covered by backward compatibility. Have you tried using the CDK from terraform? Is the pulumi plugin communicating with the terraform provider using the official gRPC interface of the provider? We do not maintain the pulumi plugin at all.
We were able to resolve it on the side of the Pulumi provider. We had to set up a Go "shim" in a way to access the Terraform Provider struct which now lives in a Go internal package.
If you compare https://pkg.go.dev/github.com/scaleway/terraform-provider-scaleway/v2@v2.38.3 and https://pkg.go.dev/github.com/scaleway/terraform-provider-scaleway/v2@v2.39.0, you will see scaleway directory is missing.
It seems this PR https://github.com/scaleway/terraform-provider-scaleway/pull/2448/files has caused this issue.
It preventing us using Pulumi because we need latest version to use VPC new routing feature. pulumiverse/pulumi-scaleway#293
The text was updated successfully, but these errors were encountered: