[Epic] Pulumi AWS 6.0

[kpitzen]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The upstream terraform AWS provider has been upgraded to the next major version - this introduces a number of breaking changes to the provider which we will track here. Additionally, there are a number of outstanding issues reported with that version of the upstream provider which we will use as a gate to inform when 6.0 is ready to be moved out of pre-release and into a full release.

Breaking changes:
https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Tasks:

• Upgrade bridge to latest version #2547
• Upgrade plugin framework to latest version #2548
• Reintroduce aws_quicksight_namespace commented out in Use Plugin Framework bridge to bring in new resources #2557
  • Fixed by Remove QuickSight related TODOs #2574
• Update implementation method of backported resources for v6 #2549
  • Fixed pulumi/aws v5.35.0 breaks cognito UserPool tags #2533
• Upgrade terraform-provider-aws to v5.7.0 #2602
• aws.sdk usage raises "NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023." #2568
• Function iam.getOpenidConnectProvider should be called getOpenIdConnectProvider #2607
• Add global replacement for "tf" prefixes #2597
• Remove deprecated resources and datasources #2613
• [v6] remove MaxItemsOne: true when appropriate #2615
• Bump java codegen to max #2616
• Name on aws.organizations.getOrganizationalUnits is "childrens" #1038
• AWS Provider v6 Dogfood Report #2626
• aws v6 incompatible with aws-apigateway pulumi-aws-apigateway#82
• v6 is incompatible with @pulumi/aws and @pulumi/aws-apigateway #2639
• Removing default tags fails to untag resources on v6 #2633
• Resolve AutoNaming warnings in the V6 release #2644
• Unexpected skip_metadata_api_check warning on v6 #2646
• Unable to set defaultTags via CLI  #2663
• Test and validate changes related to default tagging behavior #2550
• Upgrade terraform-provider-aws to v5.10.0 #2650
• Upgrade terraform-provider-aws to v5.11.0 #2665
• Panic provisioning aws:ec2:VpcEndpoint on AWS V6.0 #2658
• GetRawConfig() empty in terraform-provider-azapi pulumi-terraform-bridge#1021
• Update local examples to v6 #2674
• WAFV2 WebACL detects change when there are none in v6 alpha.5 #2664
• AWS Provider v6 Dogfood Report #2626
  -1423 [x] Audit upstream patches to find resources with upgrade risk #2710
• Create migration guide for AWS 6.0 #2546

Moved post-release tasks to #2753

Upstream issues

• [Bug]: Migrate aws_s3_object from provider 4 to 5 is not working at first apply hashicorp/terraform-provider-aws#31633
• [Bug]: existing aws_secretmanager_secret unusable after upgrade to 5.0.0 hashicorp/terraform-provider-aws#31623
• [Bug]: aws_s3_object v5 not working at all hashicorp/terraform-provider-aws#31659
• [Bug]: srarted getting Database instance is not in available state hashicorp/terraform-provider-aws#31594

Dependent issues

• Missing ARM64 support for Batch jobs #2662
• constant diff from wafv2 with no changes #1423

[t0yv0]

It would be helpful if we could move pulumi/pulumi-terraform-bridge#830 here or close it I understand the plan is to roll it out with the alpha simultaneously. Per conversation with @AaronFriel I will be closing pulumi/pulumi-terraform-bridge#981 where 830 is the one remaining item.

[WillDaSilva]

Looks like the release job failed to publish v6.0.0 of the Python SDK because the release had previously been made, then yanked: https://github.com/pulumi/pulumi-aws/actions/runs/5810390834/job/15754847261

I suspect you'll want to release a post/patch version, as I don't believe the v6.0.0 files that were uploaded to PyPI can be changed.

[aureq]

@iwahbe do we have an understanding of the breaking changes (if any) for this release please?

[iwahbe]

@iwahbe do we have an understanding of the breaking changes (if any) for this release please?

Yes. See https://www.pulumi.com/registry/packages/aws/how-to-guides/6-0-migration/.

[aureq]

Thanks @iwahbe
Do you think it could be helpful if we were providing that link as part of the GitHub release as well?