Embed SDK version

[danielrbradley]

1. Change default config to use push-based Go SDK publishing
2. Use gopatch to enable RespectSchemaVersion in all languages
3. Rebuild SDKs if we've updated the resources.go file

Related to #915 and https://github.com/pulumi/home/issues/3372

[iwahbe]

@danielrbradley Can you pick a bridged provider and deploy this code all the way through a release?

[danielrbradley]

Rolling out to pulumi-azure as a test:

• Action to create PR: https://github.com/pulumi/ci-mgmt/actions/runs/9059851553
• Azure PR: Update GitHub Actions workflows. pulumi-azure#2028
• Azure build on master: https://github.com/pulumi/pulumi-azure/actions/runs/9060891590
• Azure release: https://github.com/pulumi/pulumi-azure/actions/runs/9063178663

[danielrbradley]

A couple of warts we might want to address that I spotted during the first test rollout:

• The SDK commit actually contains all the SDKs, not only the Go SDK. This is because we just point the Go SDK publish action as the module - which is sdk/ - where the go.mod lives - which also includes all the other SDKs. This isn't a massive issue, but perhaps we could extend the action to allow globbing to select which files to include/exclude.
• Linked to the above issue, we also include the go.tar.gz file as we currently always download the assets into the sdk folder rather than a temp directory ... which results in it getting included when we publish the sdk/... go module.

[iwahbe]

A couple of warts we might want to address that I spotted during the first test rollout:

• The SDK commit actually contains all the SDKs, not only the Go SDK. This is because we just point the Go SDK publish action as the module - which is sdk/ - where the go.mod lives - which also includes all the other SDKs. This isn't a massive issue, but perhaps we could extend the action to allow globbing to select which files to include/exclude.
• Linked to the above issue, we also include the go.tar.gz file as we currently always download the assets into the sdk folder rather than a temp directory ... which results in it getting included when we publish the sdk/... go module.

I think it's worth addressing both before we deploy to all providers. I don't want to regress in download size, so we need to address the second point before deploying. For simplicity sake, I would like to address the first point as well, but it's not necessary.

but perhaps we could extend the action to allow globbing to select which files to include/exclude

Instead, can we just hard-code the list of paths we want to include? Right now, any pulumi provider should have all of their go code within sdk/{go.mod,go.sum,go}. pulumi/publish-go-sdk-action@v1 can just know that.

[danielrbradley]

I think it's worth addressing both before we deploy to all providers. I don't want to regress in download size, so we need to address the second point before deploying. For simplicity sake, I would like to address the first point as well, but it's not necessary.

Done - I make the action customisable with globs for the files to include, then customised the list of files for our use case within ci-mgmt as this might change in the future as we do things like move the go.mod one day or publish to a different repo.

Rolling out a release for the xyz provider to test this last change:

• Publish CI run: https://github.com/pulumi/pulumi-xyz/actions/runs/9078925706
• SDK Commit: https://github.com/pulumi/pulumi-xyz/tree/sdk/v1.0.0

[VenelinMartinov]

looks sensible