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
Per conversation in https://github.com/pulumi/upgrade-provider/pull/242/files it appears that maybe/possibly we're upgrading the fork of terraform-plugin-sdk to the latest from GitHub. That's may be a good option to have but it's not a good default. By default we should be trying to match whatever the bridge has when upgrading the bridge, because that is the version the bridge was tested with. Unfortunately go tooling does not make this trivial, but something along the lines of finding bridge sources and finding the go mod replace directive from those sources that the bridge was built with could do the trick. If helpful we can lift this to a text file in the bridge somehow.
Example
N/A
Output of pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
Fixes#243
After this change the terraform SDK v2 override follows the replace from
the selected bridge version exactly. I think this is what we want - this
is compensating for the inability of Go tooling to propagate the replace
to dependencies.
The change also starts to unconditionally insert this replace. This is
because on the latest bridge tfgen somehow depends on sdkv2 and even
providers such as pulumi-random that presumably do not need sdkv2 now
depend on it and need the replace accordingly, see
pulumi/pulumi-random#687 for example.
What happened?
Per conversation in https://github.com/pulumi/upgrade-provider/pull/242/files it appears that maybe/possibly we're upgrading the fork of terraform-plugin-sdk to the latest from GitHub. That's may be a good option to have but it's not a good default. By default we should be trying to match whatever the bridge has when upgrading the bridge, because that is the version the bridge was tested with. Unfortunately go tooling does not make this trivial, but something along the lines of finding bridge sources and finding the go mod replace directive from those sources that the bridge was built with could do the trick. If helpful we can lift this to a text file in the bridge somehow.
Example
N/A
Output of
pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: