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
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
This is contrary to prior requests originating from me, but I believe at the moment our deployment pipeline would benefit from never upgrading pulumi/pkg references (which installs codegen fixes) ahead of what was tested in pulumi-terraform-bridge. This makes sure additional bridge release checks such as this qualify the codegen changes on actual provider test-suites.
Affected area/feature
The text was updated successfully, but these errors were encountered:
There's some additional requirements here I think. @justinvp attempted to pre-test pulumi/pkg changes before they get released through a workflow including upgrade-provider, but the PRs failed for example:
I think the issue here is that upgrade-provider didn't respect the pre-release pulumi/pkg version that was referenced by the bridge update, thus the builds run into a compilation error.
This removes the `--kind=sdk` option from the tool.
We already have functionality to bring the pkg+sdk version in all places up to what the
bridge requires.
Fixes#184
Hello!
Issue details
This is contrary to prior requests originating from me, but I believe at the moment our deployment pipeline would benefit from never upgrading pulumi/pkg references (which installs codegen fixes) ahead of what was tested in pulumi-terraform-bridge. This makes sure additional bridge release checks such as this qualify the codegen changes on actual provider test-suites.
Affected area/feature
The text was updated successfully, but these errors were encountered: