Upgrade pulumi/pulumi

[blampe]

Bumps pu/pu across the entire repo, including a few examples that were still using very old versions.

[github-actions]

Does the PR have any schema changes?

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

Maintainer note: consult the runbook for dealing with any breaking changes.

[guineveresaenger]

While this probably works, it is not recommended to have the Pulumi version overtake the pulumi version used in the bridge.

I recommend keeping the pu/pu version currently in go.mod and updating the examples files to that.

Also this is somewhere between a missing feature in upgrade-provider and the setup of the Go tests in this repo:

• upgrade-provider does not detect all go.mod files in the examples
• this is because most providers expect a single go.mod file in `examples/, not one per example.

[blampe]

While this probably works, it is not recommended to have the Pulumi version overtake the pulumi version used in the bridge.

I recommend keeping the pu/pu version currently in go.mod and updating the examples files to that.

Good catch, updated.

Also this is somewhere between a missing feature in upgrade-provider and the setup of the Go tests in this repo:

• upgrade-provider does not detect all go.mod files in the examples
• this is because most providers expect a single go.mod file in `examples/, not one per example.

Yes, we want behavior analogous to pulumi/ci-mgmt#778 for bridged providers.

for MODFILE in $(find . -name go.mod); do pushd $(dirname $MODFILE); go get github.com/pulumi/pulumi-terraform-bridge/v3 ; go mod tidy; popd; done

I think this is essentially pulumi/upgrade-provider#142

[t0yv0]

Downgrade?

[blampe]

I think you were looking at the changes between revisions, this is upgrading from 3.55 to 3.99.

[t0yv0]

LGTM then thank you!

[t0yv0]

Yeah I'm in the process of finishing up the bridge test on 101 pulumi/pulumi-terraform-bridge#1624 - as far as I can tell the p/p codegen version passes all tests, so if you want to make an exception and move forward that's fine with me, but normally we get the p/p dependency bumped automatically through bridge updates which should be coming shortly once I'm done validating the above and clearing any blockers.

[blampe]

normally we get the p/p dependency bumped automatically through bridge updates

@t0yv0 the problem is the updates aren't comprehensive, see my other comment here #945 (comment)

[t0yv0]

Right. I thought you correctly identified the root cause on that we need to hack update-provider a little further.