-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade terraform-provider-aws to v5.75.1 #4752
Upgrade terraform-provider-aws to v5.75.1 #4752
Conversation
Does the PR have any schema changes?Found 3 breaking changes: Types
Maintainer note: consult the runbook for dealing with any breaking changes. |
Good to see the automation got past the patches this time! |
provider/go.mod
Outdated
@@ -20,7 +20,7 @@ require ( | |||
github.com/hashicorp/terraform-provider-aws v1.60.1-0.20220923175450-ca71523cdc36 | |||
github.com/mitchellh/go-homedir v1.1.0 | |||
github.com/pulumi/providertest v0.1.3 | |||
github.com/pulumi/pulumi-terraform-bridge/v3 v3.94.0 | |||
github.com/pulumi/pulumi-terraform-bridge/v3 v3.95.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is incredibly suspect, we probably should have an issue tracking this. Upstream upgrade automation should not upgrade the bridge. We want to decouple changes as much as possible so we can bisect issues easily.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah! I definitely shouldn't do both. Upgrading the bridge to 3.95.0 was already merged, so we don't have an issue here. Just need to rebase the PR
Will cut an issue in upgrade-provider about this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have cut an issue in ci-mgmt already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pulumi/ci-mgmt#1141 - I think upgrade-provider can do this, but ci-mgmt is not asking it politely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, just found the same: https://github.com/pulumi/ci-mgmt/blob/cf231765a6042eea3c4f9de32c5ecb08f23696b8/provider-ci/internal/pkg/templates/bridged-provider/.github/workflows/upgrade-provider.yml#L83
It should be configured to only upgrade the provider and not all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just rebased to remove the bridge upgrade changes from the diff
Also #4702 preventing this from going the whole way. |
e0036f9
to
d470cfc
Compare
@@ -5,7 +5,7 @@ Subject: [PATCH] Patch computed only tags for iot/billing_group | |||
|
|||
|
|||
diff --git a/internal/service/iot/billing_group.go b/internal/service/iot/billing_group.go | |||
index 90d64baff5..dd84f3acb3 100644 | |||
index 90d64baff5a..dd84f3acb33 100644 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be lovely if commits were not recorded and wouldn't churn, not sure if feasible though.
This PR has been shipped in release v6.59.1. |
This PR was generated via
$ upgrade-provider pulumi/pulumi-aws --kind=all --target-version=5.75.1
.Fixes Upgrade terraform-provider-aws to v5.75.1 #4751