Upgrade pulumi-terraform-bridge to v3.62.0 #152
Conversation
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks good to me! Reviewed entire PR up to commit fabed67
Reviewed 8 lines of code across 1 files in 28 second(s).
See details
- Skipped files: 4 (please contact us to request support for these files):
examples/go.mod,examples/go.sum,provider/go.mod,provider/go.sum - Confidence threshold:
50% - Drafted
1additional comments. - Workflow ID:
wflow_y82h3r9MC1ND4NqN
View 1 draft comments
These comments were drafted by Ellipsis, but were filtered out of the final review. They're included here so you can see our internal thought process and help you configure your ellipsis.yaml.
Drafted 1 additional comments
Filtered comment at .upgrade-config.yml:1
Notes: The change in the provider name from 'terraform-provider-awscontroltower' to 'terraform-provider-controltower' might cause issues if the new provider name is not recognized or if it doesn't exist. I need to check if 'terraform-provider-controltower' is a valid provider.
The provider name has been changed from 'terraform-provider-awscontroltower' to 'terraform-provider-controltower'. Please ensure that 'terraform-provider-controltower' is a valid provider.
Confidence changes required: 80%
Score: 0%
Something look wrong? You can customize Ellipsis by editing the ellipsis.yaml for this repository.
Generated with 鉂わ笍 by ellipsis.dev
This PR was generated via
$ upgrade-provider lbrlabs/pulumi-awscontroltower.Summary:
This PR upgrades the
pulumi-terraform-bridgeto v3.62.0 and updates theupstream-provider-namein/.upgrade-config.yml.Key points:
pulumi-terraform-bridgefrom v3.61.0 to v3.62.0.upstream-provider-namein/.upgrade-config.ymlfromterraform-provider-awscontroltowertoterraform-provider-controltower.Generated with 鉂わ笍 by ellipsis.dev